Re: 57 character limit to opngks file ?

From: Mary Haley (haley AT unknown)
Date: Wed Aug 22 2001 - 17:14:10 MDT

  • Next message: sanjay dwivedi: "ISSUe of installing V 4.2.2 on IRIX 6.5"

    > I recently changed the name of a GFLAS file used in the following code
    > running version 4.0.1
    > character qgflasfile*90
    > CALL GOPWK(9,1,3)
    > CALL GFLAS4 (1,qgflasfile)
    > CALL GFLAS3 (1)
    > CALL GCLWK (9)
    > from
    > "/users/glendeni/SOAR/MAPS/TOPO/maps.topo.CANV.gflas"
    > to
    > "/users/glendeni/SOAR/MAPS/TOPO/maps.topo.37-107+86-136.gflas"
    >
    > and got the following error messages:
    > wks.c: Error in opngks_(): Could not open /users/glendeni/SOAR/MAPS/TOPO/maps.topo.37-107+86-136.gf
    > wks.c: Error in opngks_(): Could not open /users/glendeni/SOAR/MAPS/TOPO/maps.topo.37-107+86-136.gf
    > warning:GKS:GCSGWK: --ERROR OPENING DISK FILE
    > ERROR **** IN GKS ERROR REPORTED FROM libhlu.a(Error.o)
    >
    > so there seems to be 57 character limit to the file name. That seems
    > rather short so I wanted to know if there is any way that limit can be
    > increased.

    Dear Dr. Glendening,

    Currently there is no way to increase the 57 character limit on file
    names supplied to GFLAS4. This code was written in an era when an
    eight character file name was considered bold and risky. The 57
    character limit comes from the desire to use a non-dimensioned
    CHARACTER*80 variable in the GKS call to GESC (other information
    besides the file name is being passed). At the least, an error
    message should be issued in the case that a file name is longer than
    57 characters, and the documentation should be changed to mention the
    restriction on the name length - this will be done. We are currently
    looking into whether it would be too much trouble to allow for larger
    name lengths.

    --Mary

     



    This archive was generated by hypermail 2b29 : Wed Aug 22 2001 - 21:57:40 MDT