mme gefadd
MME GEFADD is used to obtain information about the file or device associated with the file code specified in the Q register. Zero will be returned in both the A and Q registers if the file code is not defined, or if the file code is associated with a "system" PAT pointer for which there is no actual PAT body. "System" PAT pointers are created for file codes used for sysout ($REMOTE and $SYSOUT), and terminals ($DAC). Otherwise, the A register will be loaded with information about the type and state of the device, and the Q register will have information about the device address.
Originally, the information in the Q register was adequate to uniquely identify the device. However, with logical subdevices, more that 64 devices per channel, and more 4 IOM's per system, the information in the Q may no longer be adequate. Generally, a program does not need the physical address information, but if it does, PMME P.DINF may be used instead.
The Q register is set with as follows with information about the primary physical address of the device. No information is returned about alternate access paths to the same device.
MME GEFADD also stores information in the A register. The nature of this information depends on the device type, as described below.
000 -- Release 001 -- Dismount 010 -- Save 011 -- Continue
000 -- Reserved. 001 -- 132-character print line. 010 -- 136-character print line. 011 -- 160-character print line
2 -- 200 bpi 0 -- 556 bpi 1 -- 800 bpi 7 -- 1600 bpi 6 -- 6250 bpi
Tape density codes are interpreted as follows.
0000 as is (no mapping) 0001 200 bpi (NRZI mode) 0010 556 bpi (NRZI mode) 0100 800 bpi (NRZI mode) 1001 1600 bpi Phase-Encoded (PE) mode 1010 comp36 (compressed 36 track cartridge) 1011 std36 (standard 36 track cartridge) 1100 6250 bpi 1101 std18 (standard 18 track cartridge) 1110 comp18 (compressed 18 track cartridge) 1111 system high density and low density options usedSee Also:
Copyright © 2000, Thinkage Ltd.