gtpm5m1h | Messages (Online) |
GAFA0001I | DEVA SDP F.A.-xxxxxxxx |
Where:
Explanation: This is the normal response to the ZGAFA command.
System Action: None.
User Response: None.
GAFA0002T | GFS INACTIVE IN 1052/UTIL STATE |
Explanation: Get file storage (GFS) is not active in 1052 or utility (UTIL) state.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGAFA command.
GAFA0003T | INVALID FORMAT |
Explanation: The format is not valid.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGAFA command.
GAFA0004T | xxxx INVALID DEVICE CODE |
Where:
Explanation: The device code referenced in the message is not valid.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGAFA command.
GAFA0005T | yyy INVALID POOL CODE |
Where:
Explanation: The pool code referenced in the message is not valid.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGAFA command.
GAFA0006T | xxxx yyy INVALID POOL FOR THE SYSTEM |
Where:
Explanation: The pool referenced in the message is not valid for the TPF system.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGAFA command.
GAFI0006T | RECORD ID/POOL COMBINATION NOT FOUND IN RIAT |
Explanation: The ID specified in the ZGAFI command does not exist in the record ID attribute table (RIAT).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGAFI command.
GAFI0008I | input message FILE ADDRESS-fileaddr |
Where:
Explanation: This is the normal response to the ZGAFI command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGAFI command.
GAFI0009T | GFS INACTIVE IN 1052/UTIL STATE |
Where:
Explanation: Get file storage (GFS) is not active in 1052 state or utility (UTIL) state. Therefore, the ZGAFI command is not valid.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZGAFI command.
GAFI0010T | NO SON POOL IN SYSTEM |
Where:
Explanation: The ZGAFI command was entered, but no pools exist in the TPF system.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZGAFI command.
GAFI0011T | SPECIFIED RIAT TYPE IS NOT CORRECT |
Explanation: The ZGAFI command was entered with a RIAT type parameter that is not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGAFI command.
GFSP0003I | GFS SET SIZE DISPLAY |
Explanation: This is the normal response to theZGFSP DSP command with the SET parameter specified.
System Action: Processing is continued.
User Response: None.
See TPF Operations for more information about theZGFSP DSP command and an example of its output, as well as miscellaneous file pool functions.
GFSP0004I | input message -- FUNCTION PREVIOUSLY PERFORMED |
Where:
Explanation: This is the normal response to the ZGFSP OPT command when the requested function already completed.
System Action: Processing is continued.
User Response: None.
See TPF Operations for more information about the ZGFSP OPT command and miscellaneous file pool functions.
GFSP0005I | input message - PERFORMED |
Where:
Explanation: This is the normal response to a ZGFSP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGFSP commands and miscellaneous file pool functions.
GFSP0006I | GFS PARAMETER DISPLAY |
Explanation: This is the normal response to the ZGFSP DSP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZGFSP DSP command and for an example of the informational display as well as miscellaneous file pool functions.
GFSP0050E | INVALID PERCENTAGE ENTERED |
Explanation: This is the response from the ZGFSP command with either the REJ or STR parameter specified when the numeric parameter is not a valid percent.
System Action: The message is ignored.
User Response: Enter the command again and specify a valid percent value.
See TPF Operations for more information about the ZGFSP commands and miscellaneous file pool functions. See TPF Database Reference for more information about pool maintenance.
GFSP0051E | A MINIMUM OF TWO DEVICES MUST BE SPECIFIED |
Explanation: This is the response from the ZGFSP FLB or ZGFSP RTO command when only one device type is specified.
System Action: The message is ignored.
User Response: Enter the command again and specify two or more device types.
See TPF Operations for more information about the ZGFSP command and miscellaneous file pool functions. See TPF Database Reference for more information about file pool support.
GFSP0052E | NUMBER OF FILE POOL ADDRESSES NOT SPECIFIED |
Explanation: This is the response from the ZGFSP RTO command when a count of pool addresses for each device type is not specified.
System Action: The message is ignored.
User Response: Enter the command again with a count of pool addresses for each device type specified in the command.
See TPF Operations for more information about the ZGFSP RTO command and miscellaneous file pool functions. See TPF Database Reference for more information about file pool support.
GFSP0053E | UNABLE TO READ CTK9 (CYYM ERROR) |
Explanation: An error indicator was returned to the CYF1 segment from the CYYM segment while trying to retrieve keypoint 9 (CTK9).
System Action: The ZGFSP command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP command and miscellaneous file pool functions.
GFSP0056E | input message - INVALID DEVICE CODE |
Where:
Explanation: This is the response from the ZGFSP FLB or ZGFSP RTO command when the device type specified in the message is not valid for this subsystem or the TPF system.
System Action: The message is ignored.
User Response: Enter the command again and specify a valid device type.
See TPF Operations for more information about the ZGFSP FLB and ZGFSP RTO commands and miscellaneous file pool functions. See TPF Database Reference for more information about file pool support.
GFSP0057E | input message -- INVALID POOL FOR SYSTEM |
Where:
Explanation: This is the response from the ZGFSP FLB or ZGFSP RTO command when the pool type specified in the message is not valid for this subsystem or the TPF system.
System Action: The message is ignored.
User Response: Enter the command again and specify a valid pool type.
See TPF Operations for more information about the ZGFSP FLB and ZGFSP RTO commands and miscellaneous file pool functions. See TPF Database Reference for more information about file pool support.
GFSP0058E | INVALID SET VALUE ENTERED |
Explanation: This is the response from the ZGFSP SET command when the set value is out of range. The value must be between 1 and 255.
System Action: The message is ignored.
User Response: Enter the command again and specify a valid set value between 1 and 255.
See TPF Operations for more information about the ZGFSP SET command and miscellaneous file pool functions. See TPF Database Reference for more information about pool maintenance.
GFSP0059E | INVALID DEVICE TYPE IS ENTERED |
Explanation: This is the response from the ZGFSP SET command when the device type specified in the message is not valid for this subsystem or the TPF system.
System Action: The command is rejected.
User Response: Enter the command again specifying a valid device type.
See TPF Operations for more information about the ZGFSP SET command and miscellaneous file pool functions. See TPF Database Reference for more information about pool maintenance.
GFSP0060E | INVALID PROCESSOR ID |
Explanation: This is the response from the ZGFSP SET command when the processor ID specified cannot be validated. The message indicates an error was returned from the CCIDC macro.
System Action: The message is ignored.
User Response: Do one of the following:
See TPF Operations for more information about the ZGFSP SET command and miscellaneous file pool functions. See TPF Database Reference for more information about pool maintenance.
GFSP0061E | UNABLE TO FILE CTK9 (CYYA ERROR) |
Explanation: This message may be received in response to the ZGFSP SET command. An error indicator was returned to the CYF8 segment from the CYYA segment while trying to file keypoint 9 (CTK9).
System Action: The ZGFSP command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP SET command and miscellaneous file pool functions. See TPF Database Reference for more information about pool maintenance.
GFSP0062E | UNABLE TO READ CTK9 (CYYM ERROR) |
Explanation: This message may be received in response to the ZGFSP SET command. An error indicator was returned to the CYF8 segment from the CYYM segment while trying to retrieve keypoint 9 (CTK9).
System Action: The ZGFSP command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP SET command and miscellaneous file pool functions. See TPF Database Reference for more information about pool maintenance.
GFSP0063E | input message -- INVALID FUNCTION FOR 1052/UTILITY STATE |
Where:
Explanation: This is the response from the ZGFSP OPT command when the subsystem or the TPF system is in 1052 state, utility (UTIL) state, or the TPF system is cycling.
System Action: The ZGFSP command is rejected.
User Response:
See TPF Operations for more information about the ZGFSP OPT command and miscellaneous file pool functions.
GFSP0064E | input message -- POOL/DEVICE NOT IN THE CONFIGURATION |
Where:
Explanation: This is the response from the ZGFSP RCY command when the pool type specified in the message is not valid for the specified device type.
System Action: The ZGFSP command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP RCY command and miscellaneous file pool functions.
GFSP0065E | input message -- INVALID DEVICE TYPE |
Where:
Explanation: This is the response from the ZGFSP RCY command when the device type specified in the message is not valid for this subsystem or the TPF system.
System Action: The command is rejected.
User Response: Enter the ZGFSP RCY command again specifying a valid device type.
See TPF Operations for more information about the ZGFSP RCY command and miscellaneous file pool functions.
GFSP0066E | SPECIFIED POOL TYPE IS NOT VALID |
Explanation: The ZGFSP SET command was entered with a pool type specified that is not valid.
System Action: The command is rejected.
User Response: Enter the ZGFSP SET command again and specify a valid pool type.
See TPF Operations for more information about the ZGFSP SET command and miscellaneous file pool functions.
GFSP0067E | DEVICE TYPE MUST BE SPECIFIED |
Explanation: A ZGFSP command was entered to change the minimum available pools or maximum usage per minute of a pool type, but a device type was not specified. After ZPMIG CONVERT processing ends successfully, changes must be done by pool section.
System Action: The command is rejected.
User Response: Enter the ZGFSP command again and specify a valid device type.
See TPF Operations for more information about the ZGFSP and ZPMIG commands.
GFSP0068E | UNABLE TO FIND CYPDR |
Explanation: A find error occurred when the ZGFSP DSP, ZGFSP FLB, or ZGFSP RTO command tried to retrieve the pool descriptor record (CYPDR). CYPDR is contained in the #IBMML record type at ordinal #PDRON.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP commands and miscellaneous file pool functions.
GFSP0069E | UNABLE TO FILE CYPDR |
Explanation: A file error occurred when the ZGFSP FLB or ZGFSP RTO command tried to write the pool descriptor record (CYPDR). CYPDR is contained in the #IBMML record type at ordinal #PDRON.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP DSP and ZGFSP RTO commands and miscellaneous file pool functions.
GFSP0071E | UNABLE TO READ CTKB FOR PROCESSOR ORDINAL nn |
Where:
Explanation: An error occurred when the ZGFSP SET command tried to read keypoint B for an inactive processor in the loosely coupled complex.
System Action: Processing for the command ends.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP SET command
GFSP0072E | UNABLE TO FILE CTKB FOR PROCESSOR ORDINAL nn |
Where:
Explanation: An error occurred when the ZGFSP SET command tried to file keypoint B for an inactive processor. Keypoint B has been updated with a new aggregate pool carve value.
System Action: Processing for the command ends.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP SET command
GFSP0073E | FACS ERROR ON CY2KT ORDINAL nn |
Where:
Explanation: An error occurred when the ZGFSP SET command called FACS to determine the file address for the CY2KT record.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP SET command
GFSP0074E | FIND ERROR ON CY2KT ORDINAL nn |
Where:
Explanation: An error occurred when the ZGFSP SET command tried to read the CY2KT record.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP SET command
GFSP0075E | DEVICE TYPE NOT ALLOWED |
Explanation: A ZGFSP command was entered to change the minimum available pools or maximum usage per minute of a pool type with a device type specified. The ZPMIG CONVERT command must be processed successfully before changes can be done by pool section.
System Action: The command is rejected.
User Response: Enter the ZGFSP command again without a device type specified.
See TPF Operations for more information about the ZGFSP and ZPMIG commands.
GFSP0080E | - INVALID DEVICE CODE |
Explanation: This is the response to the ZGFSP DSP command when the device type in the pool descriptor record (CYPDR) is not valid for this subsystem or for the TPF system.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZGFSP DSP, ZGFSP FLB, and ZGFSP RTO commands.
GOGO0000I | GLOBAL PROCESSING COMPLETED |
Explanation: The load of the global area was completed for all the subsystem users (SSUs).
System Action: Restart processing is continued.
User Response: None.
GOGO0001I | APPLICATION FIXED CORE LOADED MODE mm SSU xxxx -- I-S yy |
Where:
Explanation: This message signals the successful end of processing for the designated subsystem user (SSU)/I-stream.
System Action: Processing is continued with the next SSU.
User Response: None.
GOGO0003E | ERROR FROM FACE ID #GLOBL ORDINAL NUMBER nnnnn SSU xxxx -- I-S yy |
Where:
Explanation: The main storage load program detected an error on return from the file address compute program (FACE).
System Action: After the message is issued, control is returned to the main storage load program, where the current subsystem user (SSU) is placed in a dormant state.
Processing is continued with the next SSU.
User Response: None.
GOGO0004E | ERROR FINDING ID zz ORDINAL NUMBER nnnnn ADDRESS aaaaaaaa SSU xxxx -- I-S yy |
Where:
Explanation: An error was detected on a FINDC macro for the record ID and file address referenced in the message for the specified subsystem user (SSU).
System Action: The current SSU is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0005E | CANNOT FIND MODE REQUESTED MODE mm SSU xxxx -- I-S yy |
Where:
Explanation: There is no match for a global load mode in the subsystem user attribute table and the main storage allocator record.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0006E | TABLES MISSING FOR CHAINED LOAD MODE mm SSU xxxx -- I-S yy |
Where:
Explanation: The GOA record header indicates chaining of records for the current load mode but the chained record cannot be found.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
See TPF System Installation Support Reference for more information about the application global area.
GOGO0007E | DIRECTORY INDEX OUT OF RANGE MODE mm SSU xxxx -- I-S yy |
Where:
Explanation: A directory index (GO1EIX) in a GOA table entry exceeds 56 for global area 1 or 68 for global area 3.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0008E | TRYING TO STRIP HEADER OF KEYPOINT RECORD MODE mm SSU xxxx -- I-S yy |
Where:
Explanation: A global record designated as keypointable must be loaded into main storage with the header intact.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0009E | TRYING TO LOAD CORE AREAS IMPROPERLY MODE mm SSU xxxx -- I-S yy |
Where:
Explanation: Globals must be loaded in the following sequence:
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0011E | COMMON RECORD DESIGNATED UNIQUE IN FIRST SSU MODE mm RECORD ID rr SSU xxxx -- I-S yy |
Where:
Explanation: A record designated as unique for the primary subsystem user (SSU) of a subsystem cannot be designated common by succeeding SSUs of that subsystem.
System Action: The current SSU is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0012E | KEYPOINTABILITY DISCREPANCY WITH FIRST SSU MODE mm RECORD ID rr SSU xxxx -- I-S yy |
Where:
Explanation: A record must be designated as keypointable in the primary subsystem user (SSU) of a subsystem before it can be designated as keypointable in succeeding SSUs of that subsystem.
System Action: The current SSU is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0013E | COMMON RECORD IDS DIFFER MODE mm CURRENT RECORD ID rr SSU xxxx -- I-S yy |
Where:
Explanation: The record ID (GO1EID) of a common record for a non-primary subsystem user (SSU) must be identical to that of the primary SSU.
System Action: The current SSU is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0014E | GLOBAL BLOCKS NOT FIRST OR IN WRONG ORDER MODE mm AREA aa SSU xxxx -- I-S yy |
Where:
Explanation: For each subsystem user (SSU), global blocks (records with GO1EID = GL) must be loaded in global area 1 or global area 3 before anything else.
System Action: The current SSU is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0015E | CORRESPONDING GLOBAL BLOCKS DIFFER IN SIZE MODE mm AREA aa SSU xxxx -- I-S yy |
Where:
Explanation: The size (GO1CON0) of a global block of a common record for a non-primary subsystem user (SSU) must be identical to that of a primary SSU.
System Action: The current SSU is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
See TPF System Installation Support Reference for more information about the application global area.
GOGO0016E | GLOBAL BLOCK UNIQUENESS INCORRECT FOR AREA MODE mm AREA aa SSU xxxx -- I-S yy |
Where:
Explanation: A common or unique record was identified as being incorrectly located in global area 1 or global area 3. Common records must be in global area 3 and unique records in global area 1.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0017E | DIRECTORY ITEM PREVIOUSLY USED MODE mm AREA aa SSU xxxx -- I-S yy |
Where:
Explanation: Each global record must have a unique directory index number (GO1EIX).
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0018E | GLOBAL CORE NOT LOADED -- UNIT TEST MODE REQUESTED SSU xxxx -- I-S yy |
Where:
Explanation: The global load mode byte for this subsystem user (SSU) is set to all zeroes. (This is intended for test purposes only and should not occur in a live TPF system.)
System Action: The current SSU is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0019E | GLOBAL LOAD ERROR, #GLOBAL RECORD HAD NO LOAD ENTRIES SSU xxxx -- I-S yy |
Where:
Explanation: The GO1ENT field of the GOA record for this SSY is zero, meaning no table entries are present.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0020E | BAD CPC OR I-STREAM NUMBER IN SUPERGOA SSU xxxx -- I-S yy |
Where:
Explanation: The CPC number (GO1CID) or I-stream number (GO1HD) found in the supergoa record does not agree with the corresponding CPC or I-stream number of the system currently in control.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.
GOGO0021E | INSUFFICIENT SPACE IN I-S SHARED GLOBAL AREA MODE mm AREA aa SSU xxxx -- I-S yy |
Where:
Explanation: The space reserved for the I-stream shared area through the system general GLOBAL macro is not sufficient to hold the record being loaded.
System Action: The current subsystem user (SSU) is placed in a dormant state. Global load is continued with the next SSU.
User Response: None.
GOGO0022E | INSUFFICIENT SPACE IN I-S UNIQUE GLOBAL AREA MODE mm AREA aa SSU xxxx -- I-S yy |
Where:
Explanation: The space reserved for the I-stream unique area through the system generation GLOBAL macro is not sufficient to hold the record being loaded.
System Action: The current subsystem user (SSU) is placed in a dormant state. Global load is continued with the next SSU.
User Response: None.
GOGO0023E | INSUFFICIENT SPACE IN EXTENDED GLOBAL AREA MODE mm AREA aa SSU xxxx -- I-S yy |
Where:
Explanation: The space reserved for the extended global area through the system generation GLOBAL macro is not sufficient to hold the record being loaded.
System Action: The current subsystem user (SSU) is placed in a dormant state. Global load is continued with the next SSU.
User Response: None.
GOGO0099I | SSU xxxx NOW DORMANT |
Where:
Explanation: This message is issued with the other GOGOnnnE messages.
System Action: The current subsystem user (SSU) is placed in a dormant state. Processing is continued with the next SSU.
User Response: None.