gtpm5m19Messages (Online)

DPAT-DSMG

DPAT0005EINVALID PROGRAM NAME

Explanation: The program name specified with the ZDPAT command is not valid for one of the following reasons:

System Action: The ZDPAT command is rejected.

User Response: Do the following:

  1. Verify the program name.
  2. Enter the ZDPAT command again and specify the correct program name.

See TPF Operations for more information about the ZDPAT command.

DPAT0010EINVALID COPY OPTION

Explanation: The copy option specified with ZDPAT command is not valid.

System Action: The ZDPAT command is rejected.

User Response: Do the following:

  1. Verify the copy option.
  2. Enter the ZDPAT command again and specify the correct copy option.

See TPF Operations for more information about the ZDPAT command.

DPAT0013EPROGRAM IS UNALLOCATED -- CANNOT PROCESS FILE COPY

Explanation: Only the Copy-C parameter is valid for unallocated programs. Unallocated programs do not have an entry in the file copy of the program allocation table (PAT).

System Action: The ZDPAT command is rejected.

User Response: Enter the ZDPAT command again and specify the Copy-C parameter.

See TPF Operations for more information about the ZDPAT functional mesasge.

DPAT0014AZDPAT CANNOT BE PERFORMED WHILE ALLOCATOR CHANGE IS IN PROGRESS -- ZDPAT ABORTED

Explanation: A ZDPAT command cannot be entered while an type loader program allocation table (PAT) change request is in progress.

System Action: The ZDPAT command is rejected.

User Response: Enter the ZDPAT command again after the TPF system completes the PAT change request.

See TPF Operations for more information about the ZDPAT command.

DPAT0101IBEGIN DISPLAY OF FILE COPY FOR IMAGE name

Where:

name
The image name.

Explanation: This is the normal response to the ZDPAT command. This message is followed by a display of the program allocation table (PAT) values for the requested program.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPAT command and an example of the informational display.

DPAT0102IBEGIN DISPLAY OF CORE COPY

Explanation: This is the normal response to the ZDPAT command. This message is followed by a display of the program allocation table (PAT) values for the requested program.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPAT command and for an example of the informational display.

DPGM0010IBEGIN DISPLAY OF FILE COPY FOR comp VERSION vv IN IMAGE name

Where:

comp
The name of the CIMR component, IPL component, or CSECT.

vv
The version code of the component.
Note:
This will only be displayed for CIMR and IPL components, and CSECTs that have an associated version code.

name
The name of the image containing the CIMR component or CP CSECT. This is not shown for IPL components.

Explanation: This is the normal response to the ZDPGM command. This message is followed by a display of the specified number of lines of data.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPGM command and for an example of the informational display.

DPLT0002IDISPLAY ASSEMBLER PGMS LOADED OR ALLOCATED xx PGMS FOUND

Where:

xx
The number of programs found in the program allocation table (PAT) and extra PAT slots.

Explanation: This is the normal response to the ZDPLT command with the BAL parameter specified. This message is followed by a list of all the programs that match the input search criteria.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPLT command and for an example of the informational display.

DPLT0003IDISPLAY ISO-C DLLS LOADED xx DLLS FOUND

Where:

xx
The number of programs found in the program allocation table (PAT) and extra PAT slots.

Explanation: This is the normal response to the ZDPLT command with the DLL parameter specified. This message is followed by a list of all the programs that match the input search criteria.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPLT command and for an example of the informational display.

DPLT0004IDISPLAY ISO-C DLMS LOADED xx DLMS FOUND

Where:

xx
The number of programs found in the program allocation table (PAT) and extra PAT slots.

Explanation: This is the normal response to the ZDPLT command with the DLM parameter specified. This message is followed by a list of all the programs that match the input search criteria.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPLT command and for an example of the informational display.

DPLT0005IDISPLAY ISO-C LIBRARIES LOADED xx LIBS FOUND

Where:

xx
The number of programs found in the program allocation table (PAT) and extra PAT slots.

Explanation: This is the normal response to the ZDPLT command with the LIBRARY parameter specified. This message is followed by a list of all the programs that match the input search criteria.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPLT command and for an example of the informational display.

DPLT0006IDISPLAY PGM NAMES LOADED OR ALLOCATED xx PGMS FOUND

Where:

xx
The number of programs found in the program allocation table (PAT) and extra PAT slots.

Explanation: This is the normal response to the ZDPLT command with the NAME parameter specified. This message is followed by a list of all the programs that match the input search criteria.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPLT command and for an example of the informational display.

DPLT0007IDISPLAY TARGET(TPF) PROGRAMS LOADED xx PGMS FOUND

Where:

xx
The number of programs found in the program allocation table (PAT) and extra PAT slots.

Explanation: This is the normal response to the ZDPLT command with the TARGET parameter specified. This message is followed by a list of all the programs matching the input search criteria.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPLT command and for an example of the informational display.

DPLT0008IDISPLAY IPAT INFORMATION IPAT CREATION TIME day mmm dd hh:mm:ss yyyy

Where:

day
The day of the week when the program allocation table (PAT) was created.

mmm
The month when the PAT was created.

dd
The day of the month when the PAT was created.

hh:mm:ss
The time of day when the PAT was created.

yyyy
The year when the PAT was created.

Explanation: This is the normal response to the ZDPLT command with the IPAT parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDPLT command.

DPLT0009EERROR IN NAME PARAMETER

Explanation: The value of the NAME parameter cannot exceed four characters and can only be less than four characters when the last character is a wildcard (*).

System Action: None.

User Response: Enter the ZDPLT command again specifying a valid value for the NAME parameter.

See TPF Operations for more information about the ZDPLT command and for an example of the informational display.

DRCT0001IAPPL CPU SS SSU STATUS

Explanation: This is the normal response to the ZDRCT command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRCT0002ESUBSYSTEM USER uuuu HAS NO ENTRIES

Where:

uuuu
The subsystem user (SSU) name (one to 4 characters).

Explanation: There are no entries in the routing control application table for the subsystem user (SSU) specified in the ZDRCT command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRCT0003ECPU c HAS NO ENTRIES

Where:

c
The CPU ID (one character).

Explanation: There are no entries in the routing control application table for the CPU ID specified in the ZDRCT command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRCT0004EAPPL aaaa IS NOT CONTAINED IN RCAT

Where:

aaaa
The application program name (one to four characters).

Explanation: The application program name specified in the ZDRCT command is not in the routing control application table.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRCT0005ESUBSYSTEM ssss HAS NO ENTRIES

Where:

ssss
The subsystem name (one to four characters).

Explanation: There are no entries in the routing control application table for the subsystem specified in the ZDRCT command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRCT0006ESUBSYSTEM NOT ACTIVE

Explanation: The subsystem specified in the ZDRCT command is not active.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRCT0007ERCAT HAS NO ENTRIES

Explanation: One of the following errors occurred:

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRCT0010ICORRECT FORMAT IS:

Explanation: The TPF system issues this message when you enter the ZDRCT command with the incorrect format. This message header is followed by a display of the various formats for the ZDRCT command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDRCT command.

DRD40067EERROR RETRIEVING RIAT

Explanation: An error occurred while retrieving the record ID attribute table (RIAT) record that contains the pool overrides.

System Action: Processing for the command is aborted and a system error (SERRC macro) is issued.

User Response: Do the following:

  1. Examine the associated dump.
  2. Take the appropriate actions.

See TPF Operations for more information about the ZRTDM commands.

DRD40068EERROR FILING RIAT

Explanation: An error occurred while filing the record ID attribute table (RIAT) record that contains the pool overrides.

System Action: Processing for the command is aborted and a system error (SERRC macro) is issued.

User Response: Do the following:

  1. Examine the associated dump.
  2. Take the appropriate actions.

See TPF Operations for more information about the ZRTDM commands.

DRD50050EUNABLE TO LOCATE RIAT RECORD ON DASD FOR ID yyyy

Where:

yyyy
The DASD ID.

Explanation: While reading the record ID attribute table (RIAT) from DASD into core, one record at a time, the last record in the chain of RIAT records was read into core but the desired record was not found. The error occurred in the DRD5 segment, which was activated by a ZRTDM command.

System Action: Processing for the command is ended and a system error (SERRC macro) is issued.

User Response: Do the following:

  1. Examine the associated dump.
  2. Take the appropriate actions.

See TPF Operations for more information about the ZRTDM commands.

DRD50056EERROR RETRIEVING RIAT DEFINITION RECORD FROM DASD

Explanation: An error occurred during a FIWHC macro while trying to retrieve the record ID attribute table (RIAT) definition record from DASD. The error occurred in the DRD5 segment, which was activated by a ZRTDM command.

System Action: Processing for the command is ended and a system error (SERRC macro) is issued.

User Response: Do the following:

  1. Examine the associated dump.
  2. Take the appropriate actions.

See TPF Operations for more information about the ZRTDM commands.

DRD50061ENO MORE SPACE IN RIAT DEFINITION RECORD - VFA DATA IGNORED FOR ID yyyy AND ALL SUBSEQUENT ENTRIES

Where:

yyyy
The ID of for the virtual file access (VFA) data.

Explanation: There is no more room in the record ID attribute table (RIAT) definition record for any more candidate definitions.

System Action: If the ZRTDM command contains multiple IDs, as many entries as can still fit into the RIAT definition record are added to this record. The virtual file access (VFA) definitions for all other IDs specified in the command are ignored.

User Response: The number of candidates in the RIAT definition record must be reduced.

See TPF Operations for more information about the ZRTDM commands and how to reduce the size of the RIAT definition record.

DRD50063EERROR RETRIEVING RIAT ID recid

Where:

recid
The record ID.

Explanation: An error occurred while retrieving the record ID attribute table (RIAT) record that contains the entry for the specified record ID.

System Action: Processing for the command is aborted and a system error (SERRC macro) is issued.

User Response: Do the following:

  1. Examine the associated dump.
  2. Take the appropriate actions.

See TPF Operations for more information about the ZRTDM commands.

DRD50064EERROR FILING RIAT ID recid

Where:

recid
The record ID.

Explanation: An error occurred while filing the record ID attribute table (RIAT) record that contains the entry for the specified record ID.

System Action: Processing for the command is aborted and a system error (SERRC macro) is issued.

User Response: Do the following:

  1. Examine the associated dump.
  2. Take the appropriate actions.

See TPF Operations for more information about the ZRTDM commands.

DREC0012IDISPLAY OF FILE ADDRESS fileaddr

Where:

fileaddr
The 16-digit hexadecimal file address.

Explanation: This is the normal response to the ZDREC command. This message is followed by a display of the requested data.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDREC command and for an example of the informational display.

DREC0020IUNIQUE COPIES OF THIS RECORD EXIST FOR OTHER I-STREAMS, PROCESSORS, OR SUBSYSTEM USERS

Explanation: This is an informational message. The record being displayed is not shared by all other I-streams, processors, and subsystem users (SSUs).

System Action: The physical record is displayed for the current (default) I-stream, processor, and SSU where the command was entered. Other copies, with different physical records, may exist for other I-streams, processors, or SSUs.

User Response: Use the IS-x CPUID-y SSU-zzzz optional keywords to display the physical record for a specific I-stream, processor, or SSU.

See TPF Operations for more information about the ZDREC command.

DSER0001I 

Explanation: This is the normal response to the ZDSER command. This message is followed by a formatted display of the system error options currently in effect.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSER command and an example of the informational display.

DSER0002I 

Explanation: This message is followed by a formatted display of the system error options currently in effect.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSER command and an example of the informational display.

DSER0042EINVALID PARAMETER -- parmx

Where:

parmx
The parameter that is not valid.

Explanation: The parameter specified in the message is not a valid parameter for the ZDSER command.

System Action: ZDSER processing is ended.

User Response: Enter the ZDSER command again with a valid parameter.

See TPF Operations for more information about the ZDSER command.

DSID0001ITHE SYSTEM ID IS enterprise.complex cpuid ON PROCESSOR num MODEL mod LOW CPU ADDRESS addr

Where:

enterprise
The name of your enterprise or operations center.

complex
The name of your loosely coupled complex or stand-alone TPF processor.

cpuid
The TPF CPU identifier.

num
The two-character version code with the six-character CPU serial number.

mod
The CPU model number, for example, 3090.

addr
The lowest CPU address of the processor or processor partition on which the TPF system is running.

Explanation: This message is displayed with the system ID, which consists of the enterprise name, complex name, CPU ID and the CPU serial number, model number, and low CPU address. It is issued by CNAL as a response to the ZDSID command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSID command and the CNAL listing.

DSID0050ESYSTEM ID DISPLAY FAILED DUE TO CTKI RETRIEVAL ERROR. INVESTIGATE CTL-0FB DUMP FROM CYYM.

Explanation: A ZDSID command was entered to display the system ID information from keypoint I. However, the CYYM segment was unable to retrieve the keypoint and issued a CTL-0FB dump.

System Action: The CNAL program (ZDSID message processor) is exited.

User Response: Have your system programmer examine the CTL-0FB dump determine the cause of the error.

See TPF Operations for more information about the ZDSID command and the CNAL listing.

DSMG0001IDDNAME ddname DEFINED

Where:

ddname
The data definition name.

Explanation: The data definition name was defined successfully.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0002IDDNAME ddname VOLUME num addr MOUNTED

Where:

ddname
A one to sixteen character data definition name.

num
The volume sequence number.

addr
The device address.

Explanation: The ZDSMG MT command is processed successfully for the data definition name, volume number, and device address specified in the message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0005Idsname

Where:

dsname
A one to 44 character data set name.

Explanation: This is the normal response to the ZDSMG VTOC command with the DISPLAY parameter specified. This message displays the data set name of the specified data set. It is displayed with the DSMG0001I and DSMG0007I messages.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG VTOC command.

DSMG0006IVOLUME NUMBER vol NUMBER EXTENTS ext

Where:

vol
A one to 64 digit volume sequence number.

ext
A one to sixteen digit number of extents on volume.

Explanation: This informational message is issued as part of a ZDSMG VTOC command request. It displays the volume number and the number of extents on the specified volume for the subject data set.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG VTOC command.

DSMG0007IVTOC SCAN COMPLETE

Explanation: The requested scan and display of the volume table of contents (VTOC) is complete.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG VTOC command.

DSMG0008IDDNAME ddname VOLUME num DISMOUNTED DSNAME dsname

Where:

ddname
A one to sixteen character data definition name.

num
The volume sequence number.

dsname
The data set name.

Explanation: The ZDSMG DM command is processed successfully for the data definition name, volume number, and data set name specified in the message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0009IDDNAME ddname DISMOUNTED DSNAME dsname

Where:

ddname
A one to sixteen character data definition name.

dsname
The data set name.

Explanation: The ZDSMG DM command is processed successfully for all volumes of the data definition name and data set name specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0010IDISPLAY COMPLETE

Explanation: The requested data set display is complete.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0012IMOUNT NOT RECORDED DUE TO SCHEDULED INITIALIZATION

Explanation: The information about the mounted data set is not recorded to file for restart because the restart control record is scheduled to be reinitialized on the next IPL.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0013ISCHEDULED GDS INITIALIZATION COMPLETED

Explanation: The requested reinitialization is complete.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG command.

DSMG0024EDEVICE ADDRESS addr NOT USABLE

Where:

addr
A symbolic device address.

Explanation: The device address specified in the message is not usable for a general data set (GDS) because:

System Action: The volume is not mounted.

User Response: None.

See TPF Operations for more information about the ZDSMG command.

DSMG0026ENO GDS MODULE ENTRIES AVAILABLE

Explanation: No unused general data set (GDS) module entries are available for the requested mount.

System Action: The volume is not mounted.

User Response: Enter the ZDMFS command to determine whether the GDS modules are in use or whether a TPF system problem is leaving modules mounted after they are dismounted.

See TPF Operations for more information about the ZDSMG MT and ZDSMG VTOC commands.

DSMG0028EI/O ERROR READING VTOC ON addr

Where:

addr
The symbolic device address (SDA).

Explanation: The TPF system found an input/output (I/O) error while trying to read the volume table of contents (VTOC) on the device specified in the message.

System Action: The volume is not mounted.

User Response: None.

See TPF Operations for more information about the ZDSMG MT and ZDSMG VTOC commands.

DSMG0029EDATA SET NAME NOT FOUND IN VTOC ON addr

Where:

addr
The symbolic device address.

Explanation: The data set name is not found in the volume table of contents (VTOC) on the device specified in the message.

System Action: The volume is not mounted.

User Response: Enter a ZDSMG VTOC command to display all data sets in the VTOC.

If the data set name is there, then a TPF system problem exists. Otherwise, the correct device address should be determined and used.

See TPF Operations for more information about the ZDSMG MT and ZDSMG VTOC commands.

DSMG0030EVOLUME NUMBER OTHER THAN 1 IS INVALID WITH ALL

Explanation: The ZDSMG DM command included the ALL keyword and a volume number other than 1. The keyword ALL is allowed only when no volume number or a volume number of 1 is specified.

System Action: The request is ignored.

User Response: Enter the command again with the correct options.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0031EVOLUME NUMBER REQUIRED IF ALL NOT SPECIFIED

Explanation: A ZDSMG DM command that does not specify a volume number does not default to ALL. A dismount request must specify what is to be dismounted.

System Action: The request is ignored.

User Response: Enter the command again with the correct options.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0032EALL WITH EITHER DDNAME OR DSNAME IS INVALID

Explanation: A ZDSMG DISPLAY command can be used to display either an explicit data definition name (DDNAME) or data set name (DSNAME), or all DDNAMES and DSNAMES, but not both.

System Action: The request is ignored.

User Response: Enter the command again with the correct options.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0033EDDNAME, DSNAME OR ALL MUST BE SPECIFIED

Explanation: A ZDSMG DISPLAY command must include at least the keyword ALL or a specific DDNAME or data set name.

System Action: The request is ignored.

User Response: Enter the command again with the correct options.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0034EFACE/FIND ERROR ON GDS CONTROL RECORD

Explanation: An error occurred while trying to access the general data set (GDS) restart control record.

System Action: The data set/volume is mounted or dismounted, as specified by the ZDSMG command. However, the status of the data set is not updated in the GDS restart records.

User Response: None.

See TPF Operations for more information about the ZDSMG MT and ZDSMG DM commands.

DSMG0035EERROR ON FILE OF GDS CONTROL RECORD

Explanation: An error occurred while trying to write the general data set (GDS) restart control record.

System Action: The data set/volume is mounted or dismounted, as specified by the ZDSMG command. However, the status of the data set is not updated in the GDS restart records.

User Response: None.

See TPF Operations for more information about the ZDSMG MT and ZDSMG DM commands.

DSMG0036IGDS INITIALIZATION SCHEDULED FOR NEXT IPL

Explanation: This is the normal response to the ZDSMG INIT command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG INIT command.

DSMG0037EINVALID TAPE NAME

Explanation: The tape name specified for the ZDSMG DEFINE command is not valid because it does not contain 3 characters.

System Action: The ZDSMG DEFINE command is ignored.

User Response: Enter the ZDSMG DEFINE command again and specify a 3-character tape name.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0038EINVALID VOLUME NUMBER -- ZERO

Explanation: A volume number of zero is specified on a ZDSMG MT or ZDSMG DM command. However, no volume 0 exists.

System Action: The request is ignored.

User Response: Enter the command again with the correct options.

See TPF Operations for more information about the ZDSMG MT and ZDSMG DM commands.

DSMG0039EINVALID SPOOL ID VALUE

Explanation: The specified spool ID is not valid.

System Action: The ZDSMG DEFINE command is ignored.

User Response: Enter the command again and specify a valid spool ID.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0040EINVALID DEFINE REQUEST, TYPE NOT SPECIFIED

Explanation: You must specify the type of medium where the data set resides when you enter the ZDSMG DEFINE command.

System Action: The ZDSMG DEFINE command is ignored.

User Response: Enter the ZDSMG DEFINE command again and specify the medium where the data set resides.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0041EINVALID DEFINE REQUEST, MORE THAN ONE TYPE

Explanation: You can specify only one data set medium for the ZDSMG DEFINE command.

System Action: The ZDSMG DEFINE command is ignored.

User Response: Enter the ZDSMG DEFINE command again and specify only one medium for the data set.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0042EINVALID GFDS VALUE. MUST BE 0 TO 59

Explanation: The general file data set number specified for the ZDSMG DEFINE command is not valid. The number must be between 0 and 59.

System Action: None.

User Response: Enter the ZDSMG DEFINE command again and specify a general file data set number between 0 and 59.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0043EINVALID USER VALUE, LENGTH EXCEEDS MAXIMUM

Explanation: The length of the value specified for the USER parameter exceeds the maximum allowed. The parameter must be between 1 and 44 characters.

System Action: The ZDSMG DEFINE command is ignored.

User Response: Enter the ZDSMG DEFINE command again and specify a USER parameter with length of 1 to 44 characters.

See TPF Operations for more information about the ZDSMG DEFINE command.

Note:
Because delimiting quotes will be removed from the USER parameter value prior to storing it in the control block, programs referencing the control block should not expect to use the terminating quote to locate the end of the value passed.

DSMG0044EDATA SET HAS MORE THAN 16 EXTENTS

Explanation: The format 1 DSCB for the specified data set states that the data set contains more than 16 extents on this volume. The TPF and IBM MVS only support a maximum of 16 extents. Therefore, the DSCB is not valid and the TPF system will not mount the volume.

System Action: The mount request for the volume is ignored. If this is the first mount for the data set, then the data set is also not mounted.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0045EVOLUME ALREADY MOUNTED

Explanation: A mount request is entered for a volume already mounted.

System Action: The request is ignored.

User Response: Enter the ZDSMG DISPLAY command to display the data definition names that were already defined and to determine how these names are being used.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0046EVOLUME NUMBER DOES NOT MATCH DSCB

Explanation: The volume number specified on the mount request does not match the volume number in the data set control block for the data set on the specified device.

System Action: The request is ignored and the device is dismounted if it was mounted for this request.

User Response: Enter a ZDSMG VTOC command to determine the volume number specified in the data set control block for the volume.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0047EINVALID FORMAT 3 DSCB FOR DATA SET

Explanation: The specified data set contains more than three extents on this volume. However, the format 3 DSCB that contains the extent descriptions has a key that is not valid.

System Action: The request is ignored and the device is dismounted if it was mounted for this request.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0048EDATA SET HAS NO EXTENTS

Explanation: The data set control block (DSCB) for the specified data set is found on the given device but the DSCB extent information is 0.

System Action: The request is ignored and the device is dismounted if it was mounted for this request.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0049EI/O ERROR READING FORMAT 3 DSCB

Explanation: An error occurred while trying to access the format 3 data set control block (DSCB) for the data set.

System Action: The request is ignored and the device is dismounted if it was mounted for this request.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0050EDDNAME NOT KNOWN TO SYSTEM

Explanation: The data definition name specified for the ZDSMG DM command is not in use. Therefore, it cannot be dismounted.

System Action: The request is ignored.

User Response: Enter the ZDSMG DM command again and specify a valid data definition name.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0051EDDNAME/DSNAME MISMATCH

Explanation: The data definition name (DDNAME) or data set name (DSNAME) is already in use with a corresponding name other than the one specified.

System Action: The request is ignored.

User Response: Enter the ZDSMG DISPLAY command to display the data definition names that were already defined and to determine how these names are being used.

See TPF Operations for more information about the ZDSMG MT and ZDSMG DM commands.

DSMG0052EDSNAME ALREADY IN USE

Explanation: The specified data set name (DSNAME) is already mounted with a data definition name (DDNAME) other than the one provided.

System Action: The request is ignored.

User Response: Enter the ZDSMG DISPLAY command to display the data definition names that were already defined and to determine how these names are being used.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0053EERROR ADDING DATA SET TO SYSTEM

Explanation: The control program found an error condition that prevented it from adding the new data set to the general data set (GDS) structure.

System Action: The data set is not mounted.

User Response: The most common reason for this message is that the control program is unable to locate a system work block (SWB). Make sure that enough SWBs are allocated to hold the number of data sets and volumes to be mounted.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0054EERROR ADDING VOLUME TO SYSTEM

Explanation: The control program found an error condition that prevented it from adding the new volume to the general data set (GDS) structure.

System Action: The volume is not mounted.

User Response: The most common reason for this return is that the control program is unable to allocate a system work block (SWB). Make sure that enough SWBs are allocated to hold the number of data sets and volumes to be mounted.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0055EVOLUME NOT MOUNTED FOR SPECIFIED DATA SET

Explanation: The specified volume is not mounted for the given data set.

System Action: The request is ignored.

User Response: None.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0056EERROR DELETING VOLUME FROM SYSTEM

Explanation: The control program found an error condition while deleting a volume for the data set from the general data set (GDS) structure.

System Action: Processing of the request is stopped.

User Response: Enter the ZDSMG DISPLAY command to determine whether the data set volume is known to the TPF system. If it is, enter the ZDSMG DM command again. If the function fails again, perform a ZDUMP for the TPF system and include the system work block (SWB) core blocks.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0057EERROR DELETING DATA SET FROM SYSTEM

Explanation: The control program found an error condition while deleting the data set from the general data set (GDS) structure.

System Action: Processing of the request is stopped.

User Response: Enter the ZDSMG DISPLAY command to determine whether the data definition name is known to the TPF system. If it is, enter the ZDSMG DM command again. If the function fails again, perform a ZDUMP for the TPF system and include the system work block (SWB) core blocks.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0058EDDNAME ALREADY IN USE

Explanation: The data definition name specified for the ZDSMG DEFINE or ZDSMG MT command is already in use.

System Action: The ZDSMG DEFINE or ZDSMG MT command is rejected.

User Response: Do the following:

  1. Enter the ZDSMG DISPLAY command to display the data definition names that were already defined and to determine how these names are being used.
  2. Enter the ZDSMG DEFINE command again and specify a unique data definition name.

See TPF Operations for more information about the ZDSMG DEFINE, ZDSMG MT, and ZDSMG DISPLAY commands.

DSMG0059EDISMOUNT ALLOWED FOR GENERAL DATA SETS ONLY

Explanation: You can use the ZDSMG DM command only to dismount general data sets (GDSs). The data definition name specified for the ZDSMG DM command was not assigned to a GDS.

System Action: The ZDSMG DM command is ignored.

User Response: Enter the ZDSMG RELEASE command to delete the data definition name from the TPF system.

See TPF Operations for more information about the ZDSMG DM and ZDSMG RELEASE commands.

DSMG0060EDDNAME NOT KNOWN TO SYSTEM

Explanation: The specified data definition name (DDNAME) is not known to the TPF system.

System Action: The display request is ignored.

User Response: None.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0062EDSNAME NOT KNOWN TO SYSTEM

Explanation: The specified data set name is not known to the TPF system.

System Action: The display request is ignored.

User Response: None.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0063EDSNAME INVALID FOR NON-GDS DEFINITION

Explanation: The specified data set name is not defined as a general data set (GDS). If you specify the DSName parameter, you must specify the name of a GDS.

System Action: The ZDSMG DISPLAY command is ignored.

User Response: None.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0067EINVALID VOLUME. VOLUME HAS NO VTOC

Explanation: The specified device has a volume table of contents (VTOC) address of zero.

System Action: The device is dismounted.

User Response: None.

See TPF Operations for more information about the ZDSMG VTOC command.

DSMG0068EI/O ERROR READING FORMAT 4 DSCB FOR VTOC

Explanation: An error is found during an attempt to read the volume table of contents (VTOC) descriptor data set control block (DSCB).

System Action: The device is dismounted.

User Response: None.

See TPF Operations for more information about the ZDSMG VTOC command.

DSMG0070EFACE ERROR ON GDS RECORD num

Where:

num
The ordinal number of the record.

Explanation: A file address compute (FACE) program error was found while trying to access the specified general data set (GDS) restart record.

System Action: The data set/volume is mounted or dismounted, as specified by the ZDSMG command. However, the status of the data set is not updated in the GDS restart records.

User Response: Determine whether enough records are allocated to the #DSCRU record type to hold the number of data sets mounted concurrently on this processor. If not, allocate more records. If there are enough records, dump the records and determine why more are needed.

See TPF Operations for more information about the ZDSMG commands.

DSMG0071EFIND ERROR ON GDS RECORD num

Where:

num
The ordinal number of the record.

Explanation: An error was found while trying to access the specified general data set (GDS) restart record.

System Action: The data set/volume is mounted or dismounted, as specified by the ZDSMG command. However, the status of the data set is not updated in the GDS restart records.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0072EGDS RECORDS FULL. MOUNT NOT RECORDED

Explanation: While trying to record the data set mount request, no free entries were found in the general data set (GDS) restart records.

System Action: The mount completes, but it is not remounted on the next IPL.

User Response: Determine whether enough records are allocated to the #DSCRU record type to hold the number of data sets mounted and defined concurrently. If not, allocate more records. If there are enough records, dump the records and determine why more are needed.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0073EGDS LOGIC ERROR. UNABLE TO LOCATE DSCB

Explanation: The TPF system is unable to locate the control block for the data set in the general data set (GDS) control structure.

System Action: The mount request is not recorded in the GDS restart data set.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0074EMISMATCH BETWEEN GDS CONTROL AND DATA RECORDS

Explanation: The control record for the general data set (GDS) restart records stated that this record has an available entry, but none is found.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0075EFILE ERROR ON GDS RECORD num

Where:

num
The ordinal number of the record.

Explanation: An error was found while trying to write the specified general data set (GDS) restart record.

System Action: The data set/volume is mounted or dismounted, as specified by the ZDSMG command. However, the status of the data set is not updated in the GDS restart records.

User Response: None.

See TPF Operations for more information about the ZDSMG MT and ZDSMG DM commands.

DSMG0076EGDS LOGIC ERROR. UNABLE TO LOCATE DATA SET ENTRY IN RECORD

Explanation: The control block for the data set stated that the restart entry for the data set was in the record just searched, but it cannot be located.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG MT and ZDSMG DM commands.

DSMG0077EGDS LOGIC ERROR. UNABLE TO LOCATE EMPTY VOLUME SLOT IN RECORD

Explanation: The entry for the data set in the restart record stated that volume entries are available. However, none were found.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0078EGDS LOGIC ERROR. UNABLE TO LOCATE VOLUME ENTRY IN RECORD

Explanation: During dismount, the control program was unable to locate the volume entry in the restart record for the volume being dismounted.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG DM command.

DSMG0079EGDS ALLOCATION ERROR. AVAILABLE COUNT INVALID

Explanation: The count of available entries in a record went negative minus while trying to record a mount request.

System Action: The count is set to 0 and the mount request is continued.

User Response: None.

See TPF Operations for more information about the ZDSMG MT command.

DSMG0080EFACE ERROR ON GDS RECORD num

Where:

num
A 1 - 4 digit decimal number. If this TPF system is loosely coupled, the #DSCRU records are for this processor.

Explanation: A file address compute (FACE) program error is returned while trying to access the displayed ordinal number as part of a general data set (GDS) restart.

System Action: The message is displayed and GDS restart is continued with the next record that exists.

User Response: Determine why the ordinal number is not valid for the #DSCRU record type for this processor.

DSMG0081EFIND ERROR ON GDS RECORD num

Where:

num
A 1 - 4 digit decimal number. If this TPF system is loosely coupled, the #DSCRU records are for this processor.

Explanation: A FIND error was received while trying to access the displayed ordinal number as part of the general data set (GDS) restart.

System Action: The message is displayed and GDS restart is continued with the next record if one exists.

User Response: Determine why the record is unable to be accessed by entering the ZDADD command.

See TPF Operations for more information about the ZDADD command.

DSMG0082EDDNAME ddname VSN vsn NOT FOUND. VOLUME NOT MOUNTED

Where:

ddname
A one to sixteen character data definition name.

vsn
The volume serial number of the missing pack.

Explanation: The pack with the volume serial number (VSN) specified in the message is required to mount the data set with the data definition name specified in the message is not found, so the data set is not mounted.

System Action: The data set is not mounted.

User Response: Determine why the volume is not found. If it can be made available, mount the data set volume by entering the appropriate ZDSMG command.

DSMG0083EDDNAME ddname NO VOLUMES FOUND. DATA SET NOT MOUNTED

Where:

ddname
A 1 to 16 character data definition name.

Explanation: No volumes are found for the data definition name specified in the message.

System Action: The data set is not mounted.

User Response: Determine why the missing volumes are not found by the IPL.

DSMG0086EGDS PRE-MOUNT ABORTED

Explanation: The general data set (GDS) reinitialization is ended because of errors while processing the pre-mount records.

System Action: The request is ended.

User Response: Using previously displayed error messages, determine why the pre-mount process failed.

DSMG0087EFIND ERROR ON PRE-MOUNT RECORD

Explanation: An error was received while trying to access one of the pre-mount data records.

System Action: Pre-mount processing is ended.

User Response: Enter the ZDPGM command to access the pre-mount records and to determine why the pre-mount process is unable to access them.

See TPF Operations for more information about the ZDPGM command.

DSMG0088EINCOMPLETE ENTRY IN PRE-MOUNT RECORD

Explanation: While processing a pre-mount record, the general data set (GDS) control program reached the end of the record before completing processing of the pre-mount entry.

System Action: Processing is stopped for this record. The next record, if one exists, is retrieved.

User Response: Enter the ZDPGM command to access the pre-mount record and to determine what is wrong with the record.

See TPF Operations for more information about the ZDPGM command.

DSMG0090EFACE ERROR ON GDS RECORD 0

Explanation: A file address compute (FACE) program error was found while trying to access the general data set (GDS) restart control record.

System Action: No GDSs are remounted. GDS restart is ended.

User Response: Determine why the FACE program is unable to generate a file address for the required ordinal number of the #DSCRU record type.

DSMG0091EFIND ERROR ON GDS RECORD 0

Explanation: An error was found while trying to access the general data set (GDS) restart control record.

System Action: No GDSs are remounted. The GDS restart is ended.

User Response: Enter the ZDSMG INIT command, which causes the GDS record to be initialized again on the next IPL from the pre-mount records. Otherwise, the record must be displayed and corrected by entering the ZAFIL or ZDFIL commands.

See TPF Operations for more information about the ZDSMG INIT, ZAFIL, and ZDFIL commands.

DSMG0092EERROR ATTEMPTING TO FILE GDS RECORD 0

Explanation: An error is found while trying to write the general data set (GDS) restart control record.

System Action: The GDS pre-mount is ended.

User Response: Using the messages from CCSONS, determine why the TPF system is unable to write the record.

DSMG0093EGDS RESTART ABORTED

Explanation: Due to errors that occurred while trying to process the general data set (GDS) restart records, restart processing is ended. Some data sets may have been mounted.

System Action: The GDS restart request is ended.

User Response: Recovery is determined from the previous error messages that describe why GDS restart was ended.

DSMG0095EUNABLE TO MIGRATE GDS

Explanation: While attempting to migrate the general data set (GDS) control records from #DSCRI to #DSCRU fixed record types, a record ID (RID) or record control check (RCC) error occurred when accessing the GDS restart control record. The error occurred for one of the following reasons:

System Action: GDS restart ends.

User Response: Enter the ZDSMG INIT command to initialize the new record type again.

See TPF Operations for more information about the ZDSMG INIT command.

DSMG0096IGDS MIGRATION COMPLETE

Explanation: Because a record ID (RID) or record control check (RCC) error occurred when accessing the general data set (GDS) restart control record, the GDS restart control records were migrated from the existing #DSCRI fixed file records to the new #DSCRU fixed file records.

System Action: GDS restart continues.

User Response: None.

DSMG0099EERROR READING MIGRATED GDS CONTROL RECORD

Explanation: The second FIND error has been received for the control record (record 0) of the #DSCRU record type. The first FIND error indicated that the records have not been initialized and caused migration processing to begin copying the #DSCRI records to the #DSCRU record type. Processing was restarted from the beginning of the restart segment and a second error occurred while reading record 0 of the #DSCRU record type.

System Action: General data set (GDS) restart is ended.

User Response: Do the following:

  1. Enter the ZDSMG INIT command to reinitialize the #DSCRU record type.
  2. Enter the ZMIGR command again.

See TPF Operations for more information about the ZDSMG INIT and ZMIGR commands.

DSMG0100IDDNAME ddname

Where:

ddname
The data definition name.

Explanation: This message precedes ZDSMG error and informational messages. It identifies the data definition to which the error or informational message pertains.

System Action: None.

User Response: None.

DSMG0104IDDNAME ddname RELEASED

Where:

ddname
The data definition name.

Explanation: The specified data definition name was successfully removed from the TPF system.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG RELEASE command.

DSMG0108ISTART OF ZDSMG DISPLAY OUTPUT

Explanation: This is the normal response to the ZDSMG DISPLAY command. This message is followed by a display of the mounted data sets.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG DISPLAY command and for an example of the informational display.

DSMG0111INO DATA SETS DEFINED

Explanation: No general data sets (GDSs) were mounted or defined. Therefore, no information can be displayed.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDSMG DISPLAY command.

DSMG0112IDEFINE NOT RECORDED DUE TO SCHEDULED INITIALIZATION

Explanation: The data definition name was not saved to file for the restart routine because the restart control record is scheduled to be initialized again the next time an initial program load (IPL) is performed.

System Action: None.

User Response: If the data definition name should be recorded, enter the ZDSMG DEFINE command after the next IPL is performed.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0153EERROR ADDING DDNAME TO SYSTEM

Explanation: An error occurred while trying to add a data definition name to the general data set (GDS) structure.

System Action: The define request is ended.

User Response: Ensure enough system work blocks (SWBs) were allocated to hold the number of data sets and volumes to be mounted or defined.

See TPF Operations for more information about the ZDSMG DEFINE command.

DSMG0157EERROR DELETING DDNAME FROM SYSTEM

Explanation: An error occurred while trying to delete a data definition name from the general data set (GDS) structure.

System Action: The release request is ended.

User Response: Do the following:

  1. Enter the ZDSMG RELEASE command again.
  2. Enter the ZDUMP command if the request fails. Include the core system work blocks (SWBs).

See TPF Operations for more information about the ZDSMG RELEASE command.

DSMG0172EGDS RECORDS FULL. DEFINE NOT RECORDED

Explanation: An attempt was made to define a general data set (GDS) but no available entries were found in the GDS restart records.

System Action: The define request completes but the GDS is not defined again during the next initial program load (IPL).

User Response: Determine whether enough #DSCRI record types were allocated to hold the number of data sets mounted or defined for this processor. If not, more records need to be allocated. If enough records were allocated, dump the records and determine why more are needed.

See TPF Operations for more information about the ZDSMG DEFINE command.