Reason:
The data area specified by INAREA= on an input operation (GET, READ, PUTGET, or WRITREAD) is too small to contain the data transmitted. The COND parameter has not been used to specify that the program will handle a truncation error. Specify a larger area or, to cause control to be returned to the program, specify TRUN on the COND parameter.
Module:
RHDCTIRH
Severity:
3
Reason:
The I/O operation was interrupted when the user hit the attention or break key. If the user specified ATTN on the COND parameter of the #TREQ macro and this condition occurs on a PUT, PUTGET, or CHECK request, control is returned to the user.
Module:
RHDCTIRH
Severity:
5
Reason:
While operating in basic (native) mode, the user has constructed a datastream containing logical errors. To capture the contents of the datastream, activate the physical I/O trace facility by means of the DCMT VARY PTERM command and attempt to recreate the problem. If the user specified LOGL on the COND parameter of the #TREQ macro and this condition occurs on a PUT, PUTGET, or CHECK request, control is returned to the user.
Module:
RHDCTIRH
Severity:
3
Reason:
A permanent I/O error has been detected. To capture the contents of the datastream, activate the physical I/O trace facility by means of a DCMT VARY PTERM command and attempt to recreate the problem. If the user specified PERM on the COND parameter of the #TREQ macro and this condition occurs on a PUT, GET, or CHECK request, control is returned to the user.
Module:
RHDCTIRH
Severity:
0
Reason:
An error has been detected in the Terminal Request Block for this request. This is a system internal error. Contact Technical Support. If the user specified INVP on the COND parameter of the #TREQ macro and this condition occurs, control is returned to the user.
Module:
RHDCTIRH
Severity:
3
Reason:
An I/O request has been issued for a terminal that is disconnected, out of service, or closed. The condition must be resolved before the I/O request can be completed. Examples of such conditions are as follows: the printer is out of paper; CRT power is off; or the terminal is not connected to the application. DCMT commands (DISPLAY/VARY) may be helpful in diagnosing and resolving the problem.
Module:
RHDCTIRH
Severity:
5
Reason:
An unrecognized completion code has been returned to the system for a terminal I/O operation. The completion code returned is not defined to the terminal I/O request handler (TIRH). This is a system internal error. If the problem occurs repeatedly, notify the system administrator, who will need to run a physical I/O trace for the terminal.
Module:
RHDCTIRH
Severity:
3
Reason:
The terminal, user, or destination has been specified incorrectly for a SEND MESSAGE request. Correct the request and reexecute the task.
Module:
RHDCTIRH
Severity:
3
Reason:
A #TREQ macro has been issued with the LTEADDR keyword specified, but the value specified is too low to be a valid LTERM address.
Module:
RHDCTIRH
Severity:
3
Reason:
A #TREQ macro has been issued with the LTEADDR keyword specified, but the value specified is too high to be a valid LTERM address.
Module:
RHDCTIRH
Severity:
3
Reason:
A #TREQ macro has been issued with the LTERMID keyword specified, but the value specified does not match the name of any LTERM in the system.
Module:
RHDCTIRH
Severity:
3
Reason:
A task has issued a terminal I/O request, but the task is not associated with a terminal.
Module:
RHDCTIRH
Severity:
3
Reason:
A task has issued a terminal I/O request, but the LTERM is not currently connected to a PTERM.
Module:
RHDCTIRH
Severity:
3
Reason:
A task has issued a new terminal I/O request, but a request for which a #TREQ CHECK macro must be issued is already in progress on that terminal.
Module:
RHDCTIRH
Severity:
3
Reason:
A #TREQ CHECK macro has been issued, but no request is currently in progress on that terminal.
Module:
RHDCTIRH
Severity:
3
Reason:
The terminal I/O request handler has been called with a Technical Request Block the first byte of which does not contain a valid type code.
Module:
RHDCTIRH
Severity:
3
Reason:
A terminal driver module has rejected a terminal I/O request as not supported for the indicated terminal.
Module:
RHDCTIRH
Severity:
3
Reason:
A #TREQ macro has been issued with the LTEADDR keyword specified, but the value specified is either an invalid address or the address of an LTE that is not connected to the task. The LTE may have been disconnected from the task if the task executed a #TREQ DISC or a #TREQ OPTIONS=LAST.
Module:
RHDCTIRH
Severity:
3
Reason:
A #TREQ WRITE/PUT macro has been issued with a negative value specified for OUTLEN. OUTLEN must be specified as a non-negative number.
Module:
RHDCTIRH
Severity:
3
Reason:
This is an informational message. The TCAM terminal receiving the message has been disconnected from DC. Probable causes include:
Module:
RHDCD0AT
Severity:
0
Reason:
The TCAM terminal attempting to connect to DC cannot complete the connection because all of the DC TCAM PTERMs are in use or varied offline. The number of TCAM terminals accessing DC exceeds the number of PTERMs SYSGENed on the TCAM LINE.
The user should either wait until a less busy time to attempt connection to DC or request that the DCA administrator increase the number of PTERMs on the LINE.
Module:
RHDCD0AT
Severity:
0
Reason:
The named map was recompiled, and either the named program has not been recompiled or the new copy of the map has not been varied online to the DC/UCF system. Recompile the program or ensure that the DCMT VARY PROGRAM NEW COPY command is issued for the map.
Module:
RHDCMAPR
Severity:
3
Reason:
An attention interrupt has been returned to DC for a terminal I/O operation. Possibly, the user hit the attention interrupt key. If this condition occurs repeatedly, notify the system administrator, who will need to run a physical I/O trace for the terminal.
Module:
RHDCMAPR
Severity:
5
Reason:
An I/O error has been returned to the system for a terminal I/O operation. If this condition occurs repeatedly, notify the system administrator, who will need to run a physical I/O trace for the terminal.
Module:
RHDCMAPR
Severity:
3
Reason:
A permanent I/O error has been returned to the system for a terminal I/O operation. If this condition occurs repeatedly, notify the system administrator, who will need to run a physical I/O trace for the terminal.
Module:
RHDCMAPR
Severity:
3
Reason:
The terminal is not responding to DC terminal I/O operations. If this condition occurs repeatedly, notify the system administrator, who will need to run a physical I/O trace for the terminal.
Module:
RHDCMAPR
Severity:
3
Reason:
This condition often indicates a programming error. Check for logic errors in program statements that reference the named map. The Map Request Block must begin with the map name.
Module:
RHDCMAPR
Severity:
3
Reason:
The named map could not be found in the DDLDCLOD area or in the load library. Ensure that the map has been compiled and link edited properly and that a BIND MAP statement has been issued for the map in the program.
Module:
RHDCMAPR
Severity:
5
Reason:
The task has been invoked from a terminal device that is not supported for the specified map. Either the map must be recompiled to support the terminal device or the task must be executed from a terminal device supported by the map.
Module:
RHDCMAPR
Severity:
5
Reason:
The named map has been found in the DDLDCLOD area or in the load (core-image) library, but it does not appear to be a map. Ensure that the named entity refers to a map and not to a different entity type (for example, a table). Also, ensure that the map is defined to the system as a map (either at system generation time or by means of a DCMT VARY DYNAMIC PROGRAM command) and that it is properly compiled and link edited.
Module:
RHDCMAPR
Severity:
5
Reason:
The user-written edit module for the indicated map field could not be found in the load library. Verify that the edit module has been properly link edited by checking the link-edit listing. Display the directory of the DC/UCF system load library (OS) or core-image library (DOS), and verify the edit module name.
Module:
RHDCMAPR
Severity:
3
Reason:
An error has occurred on a return from a user-written edit module. The probable cause is that the user edit module for the indicated map field has improperly adjusted the field pointer so that it points before the start of the field address in the output screen buffer. Ensure that the code within the user edit routine does not decrement the current address in the screen buffer. Recompile and relink the routine after correcting the code.
Module:
RHDCMAPR
Severity:
3
Reason:
The specified map is not a valid map. Use the DCMT DISPLAY PROGRAM command to verify the validity of the specified map. If necessary, recompile the map load module; ensure that the new load module is marked as the current version. If this action does not correct the problem, it is possible that the load (core-image) library has been partially destroyed. This message is similar to DC518012, which is issued when the map is a pageable map.
Module:
RHDCMAPR
Severity:
3
Reason:
The code or edit table for the indicated map field is in error. Possibly, the table either is not a code or edit table or is not linear. Defining a NOT FOUND value in a code table and a null string ('') in an edit table of valid values prevents unanticipated values from terminating the task on output.
Module:
RHDCMAPR
Severity:
3
Reason:
The automatic editing feature of the mapping facility has encountered a data error. On mapin, an error occurs if the field is required and the field contains no data. Both nonnumeric data in a field with a numeric external picture and numeric data in a field with an alphabetic external picture cause an error. Entries in a code or edit table for the field may determine that data is in error. On mapout, an error occurs if data cannot be converted to external format. Entries in a code table may determine that data is in error.
If the data is known to be correct, the external picture, internal picture, edit table, and code table for the field should be checked in terms of the automatic editing cycle in which they are used. Defining a NOT FOUND value in a code table and a null string ('') in an edit table of valid values prevents unanticipated values from terminating the task.
Module:
RHDCMAPR
Severity:
3
Reason:
A MAPIN NOIO operation has specified an I/O buffer size that is too small to accommodate the datastream. Increase the size of the buffer by using the DATASTREAM FROM option (COBOL) or the STREAML option (Assembler) so that the buffer is large enough for the physical screen size of the terminal used.
Module:
RHDCMAPR
Severity:
3
Reason:
The code or edit table for the indicated map field is in error. Possibly, the table either is not a code or edit table or is not linear. Defining a NOT FOUND value in a code table and a null string ('') in an edit table of valid values prevents unanticipated values from terminating the task on output.
Module:
RHDCMAPR
Severity:
0
Reason:
The automatic editing feature of the mapping facility has encountered a data error. On mapin, an error occurs if the field is required and the field contains no data. Both nonnumeric data in a field with a numeric external picture and numeric data in a field with an alphabetic external picture cause an error. Entries in a code or edit table for the field may determine that data is in error. On mapout, an error occurs if data cannot be converted to external format. Entries in a code table may determine that data is in error.
If the data is known to be correct, the external picture, internal picture, edit table, and code table for the field should be checked in terms of the automatic editing cycle in which they are used. Defining a NOT FOUND value in a code table and a null string ('') in an edit table of valid values prevents unanticipated values from terminating the task.
Module:
RHDCMAPR
Severity:
0
Reason:
The user-written edit module for the indicated map field could not be found in the load library. Verify that the edit module has been properly link edited.
Module:
RHDCMAPR
Severity:
0
Reason:
An error has occurred on a return from a user-written edit module. The probable cause is that the user edit module for the indicated map field has improperly adjusted the field pointer so that it points before the start of the field address in the output screen buffer. Ensure that the code within the user edit routine does not decrement the current address in the screen buffer. Recompile and relink the routine after correcting the code.
Module:
RHDCMAPR
Severity:
0
Reason:
The user program has issued a SEND verb that specifies an invalid destination, logical terminal, or user.
Module:
RHDCMAPR
Severity:
5
Reason:
A request made against a pageable map was not appropriate for the map. The probable cause is that the nonpageable variant of a map in/out request was issued rather than the pageable variant. Change the map in/out request to the corresponding paging detail, header, or resume request.
The map is considered pageable if the MCHPAGE flag is on. If the flag is off, the map is considered nonpageable.
Module:
RHDCMAPR
Severity:
3
Reason:
The named subschema load module has a wrong format.
Module:
RHDCMAPR
Severity:
3
Reason:
The input datastream is too long for the buffer defined for the user.
Increase the size of the buffer.
Module:
RHDCLINR
Severity:
3
Reason:
Either the operator hit ATTN, BREAK, or CLEAR, or the terminal is out of service.
Module:
RHDCLINR
Severity:
5
Reason:
An I/O error has occurred during an attempt to print the screen. Either a system internal error has occurred or printer logical terminals have not been defined at system generation time.
Module:
RHDCLINR
Severity:
0
Reason:
Possible causes of this error are as follows:
Module:
RHDCLINR
Severity:
3
Reason:
An IMMEDIATE form of a line mode I/O statement has been issued to a print destination, user, or logical terminal that does not exist.
Module:
RHDCLINR
Severity:
5
Reason:
An internal logic error has occurred. Print the snap dump. Contact Technical Support.
Module:
RHDCD0CB, RHDCD6CB
Severity:
3
Reason:
The indicated physical terminal is marked as out of service. Either a DCMT VARY PTERM OFFLINE command has been issued or a hardware error has occurred. A terminal that is out of service can be varied into service by means of a DCMT VARY PTERM ONLINE command.
Module:
RHDCD0CB, RHDCD6CB
Severity:
0
Reason:
The BSC2 or BSC3 terminal driver module has issued a BRAM LOPEN macro to condition the line adaptor for a physical line with the indicated relative line number, but the LOPEN was not successful. This indicates a telecommunications hardware problem.
Module:
RHDCD0CB, RHDCD6CB
Severity:
0
Reason:
The DC execution JCL does not contain a DD statement for a device that matches a physical terminal defined at system generation time.
Module:
RHDCO0CB
Severity:
0
Reason:
No corresponding physical terminal exists for the indicated device, as defined by a DD statement in the DC execution JCL. If the device should be supported by the DC system, add the appropriate PTERM statement to system generation statements. If the device should not be supported, remove the DD statement from the JCL.
Module:
RHDCO0CB
Severity:
0
Reason:
A line mode I/O request for a 3270-type device has been issued, but the screen size is not 12X40, 12X80, 24X80, 32X80, 43X80, or 27X132. The line I/O session has been canceled, and the logical terminal has been taken out of service.
Module:
RHDCLINR
Severity:
3
Reason:
An internal logic error has occurred. Print the snap dump and contact Technical Support.
Module:
RHDCD0DB, RHDCD6DB
Severity:
3
Reason:
The indicated physical terminal is marked as out of service. Either a DCMT VARY PTERM OFFLINE command has been issued, or a hardware error has occurred. A terminal that is out of service can be varied into service by means of a DCMT VARY PTERM ONLINE command.
Module:
RHDCD0DB, RHDCD6DB
Severity:
0
Reason:
The BSC2 or BSC3 terminal driver module has issued a BTAM LOPEN macro to condition the line adaptor for a physical line with the indicated relative line number, but the LOPEN was not successful. This indicates a telecommunications hardware problem.
Module:
RHDCD0DB, RHDCD6DB
Severity:
0
Reason:
The DC execution JCL does not contain a DD statement for a device that matches a physical terminal defined in DC/UCF system generation statements.
Module:
RHDCO0DB
Severity:
0
Reason:
No corresponding physical terminal exists for the indicated device, as defined by a DD statement in the DC execution JCL. If the device should be supported by the DC system, add the appropriate PTERM statement to system generation statements. If the device should not be supported, remove the DD statement from the JCL.
Module:
RHDCO0DB
Severity:
0
Reason:
The specified terminal on the specified line has been taken out of service. The probable cause is either that a communications error has occurred or that a DCMT VARY PTERM OFFLINE command has been issued. A terminal that has been varied offline can be varied back into service by means of a DCMT VARY PTERM ONLINE command.
Module:
RHDCD0EV, RHDCD6EV
Severity:
0
Reason:
This is an informational message; no action is required. A request to acquire the indicated terminal or logical unit from its present owner has been made by the VTAM SNA driver. This is most likely caused either by a DCMT VARY command or by driver startup on a terminal defined as ACQUIRE.
Module:
RHDCD0EV, RHDCD6EV
Severity:
0
Reason:
A logon for the indicated terminal or logical unit has failed, probably due to an error in the VTAM definition of the logical unit. Alternatively, the logon failure may be due to invalid session parameters or a VTAM function failure. Carefully examine the VTAM definition of the logical unit and correct any errors or inconsistencies.
Module:
RHDCD0EV, RHDCD6EV
Severity:
0
Reason:
Either the task did not supply the UIOCB address, or a zero address was specified on a #TREQ CONN or UIOCB. During any session for LINE TYPE VTAMLU, a UIOCB address must be supplied on a #TREQ CONN or #TREQ UIOCB before any other I/O request can be made.
Module:
RHDCD0EV
Severity:
3
Reason:
A task has issued a terminal I/O request, but the PTERM is not currently connected to an LTERM. For LINE TYPE=VTAMLU, every PTERM must have an associated LTERM. For more information, see the CA IDMS System Generation Guide.
Module:
RHDCD0EV
Severity:
3
Reason:
A task has issued a CONNECT or ALLOCATE request, but a PTERM with session parameters matching the requestor's UIOCB session parameters either could not be found or was found to be out of service.
Module:
RHDCD0EV
Severity:
3
Reason:
A task has issued a CONNECT request; a PTERM with session parameters matching the requestor's UIOCB session parameters was found but was already in use.
Module:
RHDCD0EV
Severity:
3
Reason:
DC has received data through the SNA driver, RHDCD0EV, and the indicated VTAM node has requested that the data be put on the local log.
Module:
RHDCD0EV, RHDCD6EV
Severity:
0
Reason:
An attempt to start a session with the named VTAM node has failed. The failure is due to improper VTAM tables (for example, the named VTAM node was not added to the VTAM tables). Various modeent problems will also cause a SIMLOGON failure (for example, the named modeent does not exist in the VTAM modeent tables, or the modeent exists but the ACB for the named VTAM node does not point to the correct modeent table). Ensure that both the VTAM table and the modeent table definitions are correct. Check the appropriate IBM documentation for further information regarding the FDBK and Sense codes
Module:
RHDCD0EV, RHDCD6EV
Severity:
0
Reason:
During open processing for the indicated line, an error has occurred on a VTAM macro. This message provides the VTAM function name, the hexadecimal values returned by VTAM in registers 0 and 15, followed by the application ID. Typically, this message indicates a VTAM generation error.
Module:
RHDCO0EV, RHDCO6EV
Severity:
0
Reason:
A DCMT VARY LINE ONLINE command for a previously open line has failed because not enough storage could be acquired for the control blocks. This condition should occur only if the system generation parameters for the line have changed since the line was shut down. Cycle the system to obtain sufficient storage to reopen the line.
Module:
RHDCO0EV, RHDCO6EV
Severity:
0
Reason:
The indicated line was defined as disabled at system generation time and therefore has not been opened. This is an informational message only.
Module:
RHDCO0EV, RHDCO6EV
Severity:
0
Reason:
During open processing for the indicated line, a PTE that did not point to an LTE was found. This condition indicates either an internal DC startup failure or an internal system generation failure. Contact Technical Support.
Module:
RHDCO0EV, RHDCO6EV
Severity:
0
Reason:
The named program was required to perform a requested function, but the program either could not be found or was found to be out of service.
Examples of this situation are as follows:
Module:
RHDCD0EV, RHDCD6EV
Severity:
0
Reason:
The indicated logical unit is waiting for a free RPL. This message is issued at the first and every 100th occurrence. The number of RPL waits should ideally be kept to zero. A large number of waits can lead to instabilities and poor performance.
Module:
RHDCD0EV
Severity:
0
Reason:
The application has issued an Advanced Program-to-Program Communication request that is invalid for the current state of the conversation. For example, a SEND_DATA was requested when the conversation was in receive state. Refer to APPC documentation, which describes the requests that can be issued for each conversation state.
Module:
RHDCAPPC
Severity:
5
Reason:
The Advanced Program-to-Program Communication request handler (CSA vector 86) has been entered with register 1 pointing to an APPC request block (#APRDS) whose type field contains an invalid value. Either vector 86 has been entered by mistake or the APR has been built incorrectly.
Module:
RHDCAPPC
Severity:
4
Reason:
The application task has issued an Advanced Program-to-Program Communication request other than ALLOCATE with an APPC resource control block that contains a resource ID of zero. However, either the PTERM does not support APPC or the task lacks a primary LTERM or PTERM. The user has probably tried to directly invoke from the terminal a task that can be started only by an APPC ALLOCATE request.
Module:
RHDCAPPC
Severity:
4
Reason:
The application program has issued an Advanced Program-to- Program Communication request specifying an APPC resource control block (#APPCDS) that does not contain a valid resource (conversation) ID in the APPCCVSA field. Either the application has failed to initialize the APPC resource control block to binary zeros before using it, or it has illegally modified the APPCCVSA field after it was set by the APPC request handler.
Module:
RHDCAPPC
Severity:
4
Reason:
The application has issued an Advanced Program-to-Program Communication request for the CONFIRM function but the synchronization level of the conversation is NONE. A CONFIRM function can be requested only if the SYNC_LEVEL is CONFIRM.
Module:
RHDCAPPC
Severity:
4
Reason:
An Advanced Program-to-Program Communication SEND_DATA request has been issued with a negative data length. The number of bytes sent by using a SEND_DATA verb must be in the range 0 to 32,767.
Module:
RHDCAPPC
Severity:
4
Reason:
The Advanced Program-to-Program Communication request handler (CSA vector 86) has been entered with register 1 pointing to an APPC request block (#APRDS) whose APRRESRC field is zero. APRRESCR should contain the address of an APPC resource control block.
Module:
RHDCAPPC
Severity:
4
Reason:
A SENDFORMATTED or RECEIVEFORMATTED operation was requested without specifying a format descriptor to guide the conversion routines. Specify an FD= parameter on the #APPC macro invocation.
Module:
RHDCAPPC
Severity:
3
Reason:
A Format Descriptor (FD) has been presented to RHDCAPPC without any Format Descriptor Elements (FDEs). This is probably due to a programming error. Specify an FD= parameter on the #APPC macro invocation.
Module:
RHDCAPPC
Severity:
3
Reason:
The number of FDEs specified in the FDH (Format Descriptor Header) does not match the number of FDEs found by RHDCAPPC. This is probably due to a programming error. Check that FDH count of FDEs matches actual count.
Module:
RHDCAPPC
Severity:
3
Reason:
A formatted SEND or RECEIVE was issued without a preceding CONTROL SESSION verb having been issued. This is probably due to a programming error. Check program logic to make certain CONTROL SESSION is issued.
Module:
RHDCAPPC
Severity:
3
Reason:
RHDCAPPC CONTROL SESSION has detected one of the following error conditions:
This is probably due to an internal error. Check the Control Session specification. This may also occur if the line quality is poor.
Module:
RHDCAPPC
Severity:
3
Reason:
RHDCAPPC SEND FORMATTED has detected one of the following error conditions:
This is probably due to an internal error. Check the SEND FORMATTED specification. This may also occur if the line quality is poor.
Module:
RHDCAPPC
Severity:
3
Reason:
RHDCAPPC RECEIVE FORMATTED has detected one of the following error conditions:
This is probably due to an internal error. Check the RECEIVE FORMATTED specification. This may also occur if the line quality is poor.
Module:
RHDCAPPC
Severity:
3
Reason:
An unexpected return code has been received in either field UIOUCM2 or APPCRETN during execution of an Advanced Program-to-Program application. Contact Technical Support with the data obtained from fields UIOUCOM and APPCRETN.
Module:
RHDCAPPC
Severity:
3
Reason:
EM62 is intended to be used only by Personal Computers connected to DC via a 3270 emulator.
Module:
RHDCEM62
Severity:
0
Reason:
A CA ADS/PC user is attempting to allocate an Advanced Program-to-Program Communication conversation via a 3270 emulation board. The DC to which he is connected, however, does not have TYPE LAPPCEMU line defined in its SYSGEN. Ask the DC system administrator to define such a line.
Module:
RHDCEM62
Severity:
0
Reason:
A CA ADS/PC user is attempting to allocate an Advanced Program-to-Program Communication conversation via a 3270 emulation board. The DC to which he is connected has a TYPE LAPPCEMU line defined but it is currently closed or out-of-service. Issue DCMT VARY LINE <name> ONLINE command.
Module:
RHDCEM62
Severity:
0
Reason:
A CA ADS/PC user is attempting to allocate an Advanced Program-to-Program Communication conversation via a 3270 emulation board. The DC to which he is connected has a TYPE LAPPCEMU line defined but all of its physical terminal elements are currently in use.
Wait and retry the ADS+/PC dialog.
Module:
RHDCEM62
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has tried to ALLOCATE a conversation with a transaction program (task) which is undefined on this DC system.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has tried to ALLOCATE a conversation with a transaction program (task) which has been defined in the DC SYSGEN as an INTERNAL task.
Rule(s) - Only EXTERNAL tasks may be allocated via APPC.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has tried to ALLOCATE a conversation with a transaction program (task) which is currently not enabled. Issue the DCMT VARY TASK <taskname> ENABLED command.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has tried to ALLOCATE a conversation with a transaction program (task) which has been defined as a map rather than a program. Only programs may be allocated.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has tried to ALLOCATE a conversation with a transaction program (task) which is in a security class to which the user does not have access. On the ALLOCATE command the user should specify the ID and password of a DC user who does have access to the task's security class.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has tried to ALLOCATE a conversation with a transaction program (task) whose program could not be located.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has ALLOCATEd a conversation with the named transaction program (task). That task has terminated abnormally before the conversation was completed.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has ALLOCATEd a conversation with the named transaction program (task). That task has terminated normally before the conversation was completed.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has tried to ALLOCATE a conversation specifying a SYNC_LEVEL higher than CONFIRM.
Module:
RHDCD0FI
Severity:
0
Reason:
A user of CA's emulated Advanced Program-to-Program Communication has ALLOCATEd a conversation with the named transaction program (task). The emulated APPC was varied out-of-service (probably by a DCMT command) while the conversation was still in progress.
Module:
RHDCD0FI
Severity:
0
Reason:
An Advanced Program-to-Program Communication transaction program running under CA's APPC Emulator has received a DEALLOCATE TYPE(ABEND) or a SEND_ERROR containing an informational message from the remote transaction.
Module:
RHDCD0FI
Severity:
0
Reason:
This is an informational message; no action is required. The message is issued each time a change is made in the number of sessions for a logical unit on an SNA line (TYPE IS VTAMLU). A request to change the number of sessions can be issued locally by means of a DCMT VARY LU command, remotely by means of a CNOS command from a remote logical unit type 6.2, or automatically at startup.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated modeent associated with the indicated logical unit has failed because the modeent is currently busy with a change request from another source. This condition is temporary; retry the change request, using a DCMT VARY LU command.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated modeent associated with the indicated logical unit has failed because the modeent has not been defined on the remote logical unit type 6.2. A modeent name defined in the DC/UCF system generation statements and defined to VTAM must also be defined to the logical unit.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated modeent associated with the indicated logical unit has failed because the remote logical unit type 6.2 has put the entire modeent out of service, disallowing the change request.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated modeent associated with the indicated logical unit has failed because an unrecognized response was received while the session values were being negotiated with the remote logical unit type 6.2. Retry the change request. If the problem recurs, contact Technical Support and your support representative for the remote logical unit device.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated modeent associated with the indicated logical unit has failed while the session values were being negotiated with the remote logical unit 6.2 device. Retry the change request. If the problem recurs, contact the systems programmer.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated logical unit has failed because a session with the remote logical unit could not be established. Verify that the logical unit exists and is currently open to VTAM.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated modeent associated with the indicated logical unit type 6.2 has failed. While negotiating the number of sessions with the logical unit, the negotiating task on the remote logical unit abended. Contact your technical support representatives responsible for the remote logical unit device.
Module:
RHDCCNOS
Severity:
0
Reason:
A request to change the number of sessions for the indicated modeent associated with the indicated logical unit has failed because the maximum number of sessions requested exceeds the number of physical terminals defined at DC/UCF system generation time with the indicated VTAM node name and modeent name. Use the DCMT DISPLAY LU MODEENT command to display the maximum number of physical terminals allowed. If more sessions are required, define additional physical terminals in system generation statements.
Module:
RHDCCNOS
Severity:
0
Reason:
The CCI line driver failed in an attempt to initialize communications with CCI. The text of the message indicates the reason for the error.
Module:
RHDCD0LV
Severity:
0
Reason:
The indicated physical terminal is marked as out of service. Either a DCMT VARY PTERM OFFLINE command has been issued, or a hardware error has occurred. A terminal that is out of service can be varied into service by means of a DCMT VARY PTERM ONLINE command. This message can be issued by any of the line driver modules.
Module:
Multiple
Severity:
0
Reason:
A Universal Communications Facility (UCF) PTERM is being disconnected from its front-end terminal in response to conditions other than the execution of a BYE command. The four-character disconnect code indicates the reason. The probable cause is that a DCMT VARY PTERM DISCONNECT/OFFLINE command has been issued for the terminal (disconnect code D901).
Module:
RHDCD0ZU
Severity:
0
Reason:
This message is issued at System startup when no BULK PTERMS are found on the UCF line. External Request Units including, Batch-to-CV, CICS-to-CV, and DC-to- DC will not operate. Terminal oriented UCF functions including UCFBatch, UCFCICS, UCF/IDMS will work.
Module:
RHDCD0ZU
Severity:
0
Reason:
An attempt is being made to connect or reconnect from a UCF front end terminal to a CA-UCF system. An error occurred while attempting to complete the connection. The error code indicates the reason for the failure as follows:
A DCMT DISPLAY MEMORY ERE may provide additional information. Note, however, that the ERE at ere-address may be reused by a different front-end connection at any time after the abort. If such reuse occurs, the information in the later display will not be relevant to the abort.
Module:
RHDCD0ZU
Severity:
0
Reason:
An error was encountered by the socket line driver RHDCD0IP. <R15-value>, <return-code> and <reason-code> are displayed in hexadecimal. <errno-code> is displayed in decimal. Documentation of the error values can be found in the CA IDMS Callable Services Guide.
Under certain circumstances, errors are acceptable. Examples are:
If the error is unexpected, contact Technical Support.
Module:
RHDCDOIP
Severity:
0
Reason:
The generic listener on the named physical terminal was successfully initiated. This message is informational only.
Module:
RHDCD0IP
Severity:
0
Reason:
The generic listener on the named physical terminal ended.
This message is informational only and is output when:
Module:
RHDCD0IP
Severity:
0
Reason:
The generic listener had to reject a connection request either because there was no BULK PTE available, or because the maximum number of connections allowed was reached.
Find out if the number of simultaneous TCP/IP connections is normal. If so, this message indicates either that additional BULK PTERM/LTERM pairs should be defined, or that the maximum number of connections should be increased.
Note: If another occurrence of this situation occurs less than one minute later, no new message is written. This is to minimize the impact of denial-of-service attacks.
Module:
RHDCD0IP
Severity:
0
Reason:
An error was encountered during the initialization of a line of type SOCKET: the SSOCKTAB table is not allocated. This is an internal error. Contact Technical Support.
Module:
RHDCD0IP
Severity:
0
Reason:
This is an internal tracing message displayed by the socket line driver RHDCD0IP when the PTERM trace for a specific LISTENER is set to 10.
Module:
RHDCD0IP
Severity:
0
Reason:
Only one line of type SOCKET can be open at a given time. This message can be displayed during startup, if more than one SOCKET line is generated with the ENABLE clause, or in response to a DCMT VARY LINE ON command, if another SOCKET line was already open.
Module:
RHDCO0IP
Severity:
0
Reason:
This warning message is displayed during the processing of a DCMT VARY <socket-line>. ON command, and TCP/IP are not active in the current IDMS environment. The line will be open, but all LISTENER and DDSTCPIP PTERMs will be out of service.
Module:
RHDCO0IP
Severity:
0
Reason:
The generic Listener on the named physical terminal is missing the mandatory TASK parameter, and will be varied out of service.
An error was encountered during the initialization of line of type SOCKET: a TASK parameter must be included in the sysgen definition of the Listener Pterm.
Module:
RHDCD0IP
Severity:
0
Reason:
On operating systems where the DNS socket functions are not available, IDMS uses its own DNS resolver. When TCP/IP is enabled in IDMS, the system reads the file associated with the SYSTCPD DDname. An invalid value was assigned to the corresponding <SYSTCPD-parameter>. The parameter is ignored.
Module:
RHDCD1IP
Severity:
0
Reason:
On operating systems where the DNS socket functions are not available, IDMS uses its own DNS resolver. When TCP/IP is enabled in IDMS, the system reads the file associated with the SYSTCPD DDname. The <error-code> error has been returned while processing the corresponding <I/O-macro> call.
Module:
RHDCD1IP
Severity:
0
Reason:
On operating systems where the DNS socket functions are not available (z/VM), or supported in a limited way (z/VSE), CA IDMS uses its own DNS resolver.
When TCP/IP is enabled in CA IDMS, the system reads the file associated with the SYSTCPD DDname. Either the SYSTCPD DDname was not defined in the JCL, or the corresponding file was empty.
<action> depends on the operating system.
Module:
RHDCD1IP
Severity:
0
Reason:
IDMS is processing the displayed socket request. The request is taking a long time before it returns control. In most cases, name server (DNS) functions can take a long time to complete. Possible reasons for a bad response time are:
Additional information is displayed in the message, following the <socket-function>: the corresponding taskid, taskcode, userid, lterm and the current TCPIP stack. For the DNS specific socket functions, the requested hostname or IPaddress is displayed too.
Module:
Ticker, on behalf of RHDCD1IP
Severity:
0
Reason:
Informational message displayed when TCP/IP is enabled in the IDMS system, just before checking the status of the TCP/IP stacks. Is followed by message DC088025. Status of TCP/IP stack <jobname> is <status> where <jobname> is the name of the job which activates the stack where <status> can be either active, inactive or excluded.
Module:
RHDCD1IP
Severity:
0
Reason:
Informational message displayed when TCP/IP is enabled in the IDMS system, just after checking the status of the TCP/IP stacks. Is preceded by message DC088024.
<jobname> is the name of the job which activates the stack
<status> can be either active, inactive or excluded.
Module:
RHDCD1IP
Severity:
0
Reason:
A server type application running without any TCP/IP stack affinity had to reject a connection request because that connection was explicitly addressed to a TCP/IP stack that was excluded from the IDMS environment. The server application remains ready to accept new connections. The count value represents the number of connections rejected for this application running under the specified lterm.
Module:
RHDCD1IP
Note: If another occurrence of this situation occurs less than one minute later, no new message is written. This is to minimize the impact of denial-of-service attacks.
Severity:
0
Reason:
An internal error has occurred when validating the TCP/IP stack owning the socket corresponding to a new accepted connection received by a server type application. This situation may happen with a server application running without any TCP/IP stack affinity, in an IDMS environment where TCP/IP stacks have been excluded.
This is an internal error. Contact Technical Support, and provide them with the small snapshot of an internal work area that is written in the log file, just after this error message.
Module:
RHDCD1IP
Severity:
0
Reason:
The stack name assigned to the default stack in SYSGEN is not active in the current IDMS system.
Possible reasons are:
The default stack will be assigned to the system default, if it is currently active (i.e., not excluded), or to the first active stack from the list.
Module:
RHDCD1IP
Severity:
0
Reason:
This warning message is displayed during startup to indicate that even without the definition of the new TCP/IP SYSGEN entity introduced in r17, TCP/IP support is still enabled in the current environment. For compatibility with r16, if the new TCP/IP entity is not defined into SYSGEN, but the same system does contain the definition of an enabled SOCKET line, then TCP/IP is automatically enabled during startup.
It is recommended that the user defines the new TCP/IP SYSGEN entity to set all the different TCP/IP features supported by IDMS.
Module:
RHDCD1IP
Severity:
0
Reason:
DDS communication using TCP/IP has been established between the source node and <target-nodename>.
Module:
RHDCD0IP
Severity:
0
Reason:
DDS communication using TCP/IP has been stopped between the source node and <target-nodename>.
Module:
RHDCD0IP
Severity:
0
Reason:
DDS communication using TCP/IP has been established between the <source-nodename> and the target system. The target system is now ready to process DDS requests coming from <source-nodename>.
Module:
RHDCD0IP
Severity:
0
Reason:
During the vary offline processing of the DDSTCPIP PTE <pterm-id>, the DDS internal resources used by the <lterm-id> LTE are released.
Module:
RHDCD0IP
Severity:
0
Reason:
During the establishment of a new TCP/IP connection for use by a DDS request, the specified port number <port#> cannot be used, probably because it is already in use by another application in the system. <port#> is a port number belonging to the PORT RANGE parameter defined on the DDSTCPIP PTE <pterm>. After this warning message is displayed, the IDMS system always tries to use the next port number from the defined port range.
Module:
RHDCD0IP
Severity:
0
Reason:
An error was encountered by the socket line driver RHDCD0IP, when trying to establish DDS communication using TCP/IP.
This is an internal error. Contact Technical Support.
Module:
RHDCD0IP
Severity:
0
Reason:
The DDSTCPIP pterm does not contain any target host definition, that is, no target name or no target IP-address. This information is required to establish DDS communication with a target node name.
Module:
RHDCD0IP
Severity:
0
Reason:
The DDS control connection associated with the DDSTCPIP pterm has been closed by the target DDS system. The corresponding PTERM in the local system is varied out of service.
Module:
RHDCD0IP
Severity:
0
Reason:
The target IDMS nodename associated with the DDSTCPIP pterm does not have a valid entry in the local NODE table; either the node name is not present in the table, or the associated access method is not TCP/IP. The corresponding PTERM in the local system is varied out of service.
Module:
RHDCD0IP
Severity:
0
Reason:
The DDSTCPIP pterm cannot be varied online because another DDS connection already exists between this local IDMS system and the corresponding IDMS target node name.
Module:
RHDCD0IP
Severity:
0
Reason:
An invalid condition has been found on the DDS control connection associated with the DDSTCPIP pterm. This is an internal error. Contact Technical Support.
Module:
RHDCD0IP
Severity:
0
Reason:
The SERVICES FILE option on the TCP/IP SYSGEN statement specifies the name of the services file that must be used to process the GETSERVBYNAME and GETSERVBYPORT socket functions. When TCP/IP support is enabled in the IDMS system, during startup or dynamically using the DCMT command, IDMS reads the file associated with the DDname specified on the SERVICES FILE option, and builds the services table in internal memory. The <error-code> error has been returned while processing the corresponding <I/O-macro> call..
Module:
RHDCD1IP
Severity:
0
Reason:
The SERVICES FILE option on the TCP/IP SYSGEN statement specifies the name of the services file that must be used to process the GETSERVBYNAME and GETSERVBYPORT socket functions. When TCP/IP support is enabled in the IDMS system, during startup or dynamically using the DCMT command, IDMS reads the file associated with the DDname specified on the SERVICES FILE option, and builds the services table in internal memory. Either the specified DDname was not defined in the JCL, or the corresponding file was empty.
The GETSERVBYNAME and GETSERVBYPORT socket functions will not be available in the IDMS system
Module:
RHDCD1IP
Severity:
0
Reason:
The SERVICES FILE option on the TCP/IP SYSGEN statement specifies the name of the services file that must be used to process the GETSERVBYNAME and GETSERVBYPORT socket functions. When TCP/IP support is enabled in the IDMS system, during startup or dynamically using the DCMT command, IDMS reads the file associated with the DDname specified on the SERVICES FILE option, and builds the services table in internal memory. An internal error has been detected during this processing. Please contact Technical Support, and provide them with the different snapshots of the internal work areas that are written in the log file, just before this error message. The titles of the different snapshots all start with the same "SERVICES table" string.
Module:
RHDCD1IP
Severity:
0
Reason:
The SERVICES FILE option on the TCP/IP SYSGEN statement specifies the name of the services file that must be used to process the GETSERVBYNAME and GETSERVBYPORT socket functions. When TCP/IP support is enabled in the IDMS system, during startup or dynamically using the DCMT command, IDMS reads the file associated with the DDname specified on the SERVICES FILE option, and builds the services table in internal memory. An invalid record has been read from the SERVICES file. The standard record definition for the services file is : <service-name> <port#>/<protocol> <alias1> <alias2> ... where the aliases are optional.
This is a warning message. The record is simply ignored, and the next record from the file is read and used to build the internal services table.
Module:
RHDCD1IP
Severity:
0
Invalid service name found on record <recnum> from SERVICES file.
Reason:
The SERVICES FILE option on the TCP/IP SYSGEN statement specifies the name of the services file that must be used to process the GETSERVBYNAME and GETSERVBYPORT socket functions. When TCP/IP support is enabled in the IDMS system, during startup or dynamically using the DCMT command, IDMS reads the file associated with the DDname specified on the SERVICES FILE option, and builds the services table in internal memory. An invalid service name or alias name has been found on the record number <recnum> from the services file. A valid service or alias name may not exceed 256 characters, and a service name must also start in column 1.
This is a warning message. The record is simply ignored, and the next record from the file is read and used to build the internal services table.
Module:
RHDCD1IP
Severity:
0
Reason:
The SERVICES FILE option on the TCP/IP SYSGEN statement specifies the name of the services file that must be used to process the GETSERVBYNAME and GETSERVBYPORT socket functions. When TCP/IP support is enabled in the IDMS system, during startup or dynamically using the DCMT command, IDMS reads the file associated with the DDname specified on the SERVICES FILE option, and build the services table in internal memory. An invalid port number has been found on the record number <recnum> from the services file. A valid port number may be any value between 1 and 65535.
This is a warning message. The record is simply ignored, and the next record from the file is read and used to build the internal services table.
Module:
RHDCD1IP
Severity:
0
Reason:
The SERVICES FILE option on the TCP/IP SYSGEN statement specifies the name of the services file that must be used to process the GETSERVBYNAME and GETSERVBYPORT socket functions. When TCP/IP support is enabled in the IDMS system, during startup or dynamically using the DCMT command, IDMS reads the file associated with the DDname specified on the SERVICES FILE option, and build the services table in internal memory. An invalid protocol has been found on the record number <recnum> from the services file.
The valid protocols are TCP and UDP, or any combinations of lower- and upper-cases that form those two names.
This is a warning message. The record is simply ignored, and the next record from the file is read and used to build the internal services table.
Module:
RHDCD1IP
Severity:
0
Reason:
An error has been detected during the initialization or termination of the TCP/IP environment in CA IDMS. <operation> can be initialization or termination. The error message displays also the corresponding <errno-code> and <reason-code> values.
Module:
RHDCD1IP
Severity:
0
Reason:
The initialization of the TCP/IP environment in CA IDMS has just been started. This can happen during startup of the IDMS system, or during the processing of a DCMT VARY TCP/IP STATUS ON command.
Module:
RHDCD1IP
Severity:
0
Reason:
The initialization of the TCP/IP environment in CA IDMS is completed without any errors. TCP/IP is active.
Module:
RHDCD1IP
Severity:
0
Reason:
The initialization of the TCP/IP environment in CA IDMS is terminated, and TCP/IP is not active. Possible reasons are:
The message DC088070 is normally displayed prior to this one, showing the exact ERRNO and REASON error codes.
Module:
RHDCD1IP
Severity:
0
Reason:
The termination of the TCP/IP environment in CA IDMS has just been started. This can happen during shutdown of the IDMS system, or during the processing of a DCMT VARY TCP/IP STATUS OFF command.
Module:
RHDCD1IP
Severity:
0
Reason:
The termination of the TCP/IP environment in CA IDMS is completed without any errors. TCP/IP is no longer active.
Module:
RHDCD1IP
Severity:
0
Reason:
The termination of the TCP/IP environment in CA IDMS has been aborted because the quiescing of TCP/IP was canceled or the associated timeout expired, and the KEEP option was requested. TCP/IP is back active.
Module:
RHDCD1IP
Severity:
0
Reason:
The quiescing of the TCP/IP environment has been interrupted. Either it was canceled using a DCMT VARY TCP/IP STATUS CANCEL command, or the timeout associated with the DCMT VARY TCP/IP STATUS OFF QUIESCE command was expired. As the KEEP option was specified on the QUIESCE or CANCEL command, the TCP/IP status is varied back to ON.
Module:
RHDCD1IP
Severity:
0
Reason:
The quiescing of the TCP/IP environment has been interrupted. Either it was canceled using a DCMT VARY TCP/IP STATUS CANCEL command, or the timeout associated with the DCMT VARY TCP/IP STATUS OFF QUIESCE command was expired. As the FORCE option was specified on the QUIESCE or CANCEL command, the TCP/IP status is forced to OFF.
Module:
RHDCD1IP
Severity:
0
Reason:
This is the tracing message written to the log file when the TCP/IP trace facility with the CALL option is requested for an LTERM. For all read and write SOCKET functions, an additional LENGTH parameter with the corresponding read or written length value is added at the end of the message. If <return-code> is different from 0 or -1, it is displayed in hexadecimal. <errno-code> is always displayed in decimal. <reason-code> is always displayed in hexadecimal.
Module:
RHDCSOCK
Severity:
0
Reason:
This is the tracing message written to the log file when the TCP/IP trace facility with the CALL option is requested for an LTERM. This message is used only by specific socket functions reserved for the system. <R15-value> is displayed in hexadecimal.
Module:
RHDCSOCK
Severity:
0
Reason:
This is the tracing message written to the log file when the TCP/IP trace facility with the CALL option is requested for an LTERM, and the current socket function is invalid.
Module:
RHDCSOCK
Severity:
0
Reason:
This message is exactly the same than DC088100, but is used for all socket functions called internally by the IDMS system. Refer to message DC088100 for an explanation of all the parameters.
Module:
RHDCD1IP
Severity:
0
Reason:
This message is exactly the same than DC088101, but is used for all socket functions called internally by the IDMS system. Refer to message DC088101 for an explanation of all the parameters.
Module:
RHDCD1IP
Severity:
0
Reason:
The driver task for the specified terminal line has terminated.
Control blocks for the line have been closed. Possible causes are as follows:
Module:
RHDCC00A
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|