Tony writes:

>+-F-I-L-E---I-N-F-O-R-M-A-T-I-O-N---D-I-S-P-L-A-Y+
>!  FILE NAME IS ANYFILE.GROUP.ACCOUNT            !
>!  FOPTIONS: SYS,ASCII,FORMAL,F,NOCCTL,FEQ,KXL   !
>!            NOLABEL                             !
>!  AOPTIONS: INPUT,NOMR,LOCK,DEF,BUF,NOMULTI     !
>!            WAIT,NOCOPY                         !
>!  DEVICE TYPE: 3      DEVICE SUBTYPE: 8         !
>!  LDEV: 53       DRT: 8         UNIT: 0         !
>!  RECORD SIZE: 214    BLOCK SIZE: 4096  (BYTES) !
>!  EXTENT SIZE: 3964   MAX EXTENTS: 8            !
>!  RECPTR: 1           RECLIMIT: 10000           !
>!  LOGCOUNT: 4            PHYSCOUNT: 0           !
>!  EOF AT: 4081        LABEL ADDR: %00000000000  !
>!  FILE CODE: 0        ULABELS: 0                !
>!  FILE OWNER: MGR.ETRAN60                       !
>!  PHYSICAL STATUS: ????????????????             !
>!  ERROR NUMBER: 0     RESIDUE: 0                !
>!  BLOCK NUMBER: 0            NUMREC: 18         !
>+------------------------------------------------+
>
>My question is, what is the physical status represent?, and does the
>"???????" pose any problems?? Thanks in advance!


For files that are not KSAM nor terminals PRINTFILEINFO (a CM function)
will attempt to retrieve the device status via a call to ATTACHIO. If the
device responds back the "??" will be replaced with that numeric value.

In the example here the file is KSAM as indicated by the FOPTIONS "KXL"
so we never even asked.

Hope this helps!

Bill
HP/CSY