|
|
|
Reason:
This message is written to the CICS log by the PLT initialization/shutdown program. It is issued if the PLT program was unable to issue an INQUIRE SYSTEM command to determine system status.
System Action:
The PLT program was terminated.
User Action:
Verify that the CICS agent has been installed correctly and that the PLT program is authorized to issue INQUIRE SYSTEM commands.
Reason:
This message is written to the CICS log by the PLT initialization program. It is issued if the PLT program was unable to start the SVCI transaction.
System Action:
The PLT program is terminated, and SVCI is unavailable.
User Action:
Verify that the CICS agent has been installed correctly and that the PLT program is authorized to start the SVCI transaction. Also check that the SVCI transaction and programs are defined to CICS and are enabled.
Reason:
This message is written to the CICS log by the PLT initialisation program after it has issued the transaction start request. This message is followed by the RCIS06 message when SVCI registers as the PPI receiver.
System Action:
None.
User Action:
None.
Reason:
This message is issued if the PLT program is called at any other time than during CICS initialisation or termination. This should not occur. aaaaaa describe the current CICS processing stage.
System Action:
The program is terminated.
User Action:
Investigate why the program was called.
Reason:
A request received by the database inquiry processor could not be processed because the request was invalid or the database type is not supported.
System Action:
The request is rejected.
User Action:
Ensure that the database inquiry request is valid and for a valid database type.
Reason:
This message is sent in response to an ADABAS inquiry. The message text indicates the database status.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to a PSB inquiry when the DLI status code indicates that all resources referenced by the specified PSB area are available.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to a PSB inquiry when the DLI status code indicates that some resources referenced by the specified PSB area are unavailable.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to a DB2 inquiry. It indicates that the DB2 interface is available to CICS.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to a DB2 inquiry. It indicates that the DB2 interface is not available to CICS.
System Action:
None.
User Action:
Issue the required DB2 commands to enable the DB2 interface.
Reason:
The record received by the CICS PPI receiver could not be recognized as a valid $RMXPPI MDO. An indication of what was wrong is given in the reason code. The values are as follows:
0001 Record is smaller than 8 bytes.
0002 MDO length is inconsistent with size of record received.
0003 MDO key is not recognized.
0004 Request type is not valid.
0005 Record is not a CICS request.
System Action:
Request is ignored.
User Action:
Contact your support representative.
Reason:
PPI communications could not be started because PPI services are unavailable. This message is written to the system log.
System Action:
SVCI waits for 1 minute before retrying.
User Action:
Ensure that PPI is started.
Reason:
A serious error occurred. RC=xx shows the PPI return code.
System Action:
The transaction is terminated.
User Action:
Verify that SVCI and PPI are installed correctly.
Reason:
A request to modify unsolicited message filters on CICS region cccccccc was rejected because unsolicited message flow is inactive.
System Action:
Request is ignored.
User Action:
Contact your support representative.
Reason:
The CNMNETV module could not be loaded. The product is probably not installed correctly. This message is written to the system log.
System Action:
The transaction is terminated.
User Action:
Verify that SVCI and PPI are installed correctly.
Reason:
This message is written when SVCI registers as a PPI receiver successfully. xxxxxxxx is the receiver ID, and aaaaaaaa is the CICS job name. This message is written to the system log and the SOLVCICS PPI queue.
System Action:
SVCI waits for command request.
User Action:
None.
Reason:
A request to stop unsolicited message processing was received by SVCI and is being processed.
System Action:
SVCI notifies the transient data exit to clean up.
User Action:
None.
Reason:
A request to modify unsolicited message delivery was processed successfully.
System Action:
Future unsolicited message selection will be based on the modified filter criteria.
User Action:
None.
Reason:
A request to stop the delivery of unsolicited messages was processed successfully.
System Action:
Unsolicited message flow is terminated.
User Action:
None.
Reason:
This message displays the status of unsolicited message delivery. cccccccc is the job name of the CICS region, rrrrrrrr is the unsolicited receiver ID, and jjjjjjjj is the job name of the region that initiated the unsolicited message exit. aaaaaaa is either ACTIVE or INACTIVE.
System Action:
None.
User Action:
None.
Reason:
An attempt to interrogate the unsolicited message exit failed. nnnnnn is the EIBRCODE (in hexadecimal format) returned to SVCI by CICS. This message might be sent in response to a status request when the unsolicited message exit is disabled.
System Action:
None.
User Action:
If you cannot determine the reason for the failure, contact your support representative.
Reason:
An attempt to start unsolicited message flow was rejected because the flow is already active.
System Action:
The request is rejected.
User Action:
None.
Reason:
This message is written to the CICS log if an attempt is made to manually start the SVCI transaction while the task is already active.
System Action:
The request is terminated.
User Action:
Only start the SVCI transaction if an SVCI transaction is not already active in the CICS region.
Reason:
This message is sent in response to an SVCI command request. It indicates that the command processing transaction SCMD could not be started. nnnnn is the EIBRCODE returned in response to the EXEC CICS START request.
System Action:
The command request fails.
User Action:
Check the RCODE value to determine the reason for the request failure. Check that SCMD is available and installed.
Reason:
The SVCI is posted by the PLT shutdown program to allow CICS shutdown to continue. xxxxxxxx is the CICS PPI receiver ID, and aaaaaaaa is the CICS job name.
System Action:
SVCI transaction terminates.
User Action:
None.
Reason:
An attempt to start the SVCI transaction manually resulted in the transaction being started as a long running background task.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the transient data exit. The PPI connection for unsolicited messages has failed. ccccccc is the CICS job name, and xx is a PPI return code.
System Action:
Unsolicited message flow is interrupted. However, the transient data exit remains active.
User Action:
Correct the reason for PPI unavailability. This may be because the PPI service has terminated or because the receiver has been stopped.
Reason:
The transient data exit was enabled with an invalid global area. cccccccc is the CICS job name. This message indicates an internal error in SVCI, probably due to installation errors.
System Action:
None.
User Action:
Verify SVCI installation.
Reason:
The transient data exit acquires storage for formatting the messages from the transient data queue. It is unable to acquire storage and has disabled the unsolicited message flow.
System Action:
Unsolicited message flow is interrupted. However, the transient data exit remains active.
User Action:
Ensure that there is sufficient storage in the CICS address space for the exit to run. Usually, the amount of storage required by the exit is less than 1 kilobyte.
Reason:
The record received by the CICS PPI receiver could not be recognized as a valid $RMXPPI MDO. An indication of what was wrong is given in the reason code (see the reason code explanation for the RCIS01 message).
System Action:
Request is ignored.
User Action:
Contact your support representative.
Reason:
A request to execute a CICS command failed because the request was not authorized.
System Action:
Request is rejected.
User Action:
Make sure that SVCI is correctly authorized.
Reason:
A serious error occurred. RC=xx shows the PPI return code.
System Action:
The command response cannot be sent.
User Action:
Make sure that the PPI interface is available to CICS.
Reason:
The command received by the CICS PPI receiver could not be recognized as a valid SVCI command. An indication of what was wrong is given in the reason code. The values are:
0007 No parameters on command
0008 Invalid command (must be INQ, SET, or PER)
0009 No resource type specified on command
0010 Resource name too long (more than 8 characters)
0011 Invalid option specified
0012 No option specified on SET command
0013 Options not allowed on INQ command
0014 Invalid resource type
0015 Invalid option on SET command
0016 Invalid task number in SET TASK command
System Action:
Request is rejected.
User Action:
Correct the command syntax.
Reason:
This message is sent in response to an INQUIRE FILE request.
vvvv is the file type: VSAM, BDAM, or RMT (remote).
dddddddd is the ddname.
ACC is a list of the file access authorities.
DSN is the dataset name.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to a SET request.
Is the resource type (for example, FILE, TRAN, or CONN).
Is the resource name.
Are the option values which were set.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to an INQUIRE TRAN request.
tttt is the transaction name.
pppppppp is the transaction program name.
sss is the transaction status.
cccccccc is the transaction class.
nnn is the transaction priority.
The following information is displayed for a remote transaction:
ssss is the SYSID of the remote system.
rrrrrrr is the name by which the transaction is known on the remote system.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to an INQUIRE CONN request.
cccc is the connection name.
nnnnnnnn is the network name for the connection.
sss is the service status (either INS or OUT).
acq indicates whether the connection is acquired or released.
accm is the access method for the connection (that is, VTAM, IRC, IND, or XM).
APPC is present for VTAM APPC connections.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to an INQUIRE VTAM request.
sss indicates whether the CICS VTAM ACB is open or closed.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to an INQUIRE TERMINAL request.
accm is the terminal access method.
tttt is the CICS terminal ID.
sss indicates whether the terminal is in service or out of service.
aaa indicates the terminal acquire status.
ati indicates the terminal ATI status.
netname is the name by which the terminal is known in the network.
tran is the ID of the transaction running at this terminal.
userid is the ID of the user signed on to the terminal.
mode is the logmode name for an LU 6.2 session.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to an INQUIRE TASK request.
taskno is the CICS task number.
tran is the ID of the transaction associated with the task.
sta indicates the task status.
userid is the ID of the user currently associated with the task.
termid is the name of the terminal on which the task is running.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response to an INQUIRE IRC request.
sss indicates whether the IRC is open or closed.
System Action:
None.
User Action:
None.
Reason:
This message is written if a TASK PURGE request was unsuccessful.
nnnnnnn is the task number.
rrrrrrrrrr indicates the reason why the purge failed.
System Action:
The request is rejected.
User Action:
Some tasks are not purgeable.
Reason:
This message is written if a TASK PURGE request was successful.
nnnnnnn is the task number.
System Action:
None.
User Action:
None.
Reason:
This message is written in response to a PERFORM SHUTDOWN request to SVCI. The response is sent before the shutdown command is processed.
System Action:
SVCI continues with CICS shutdown.
User Action:
None.
Reason:
This message is written if no resources were found for an SVCI request.
System Action:
The request is rejected.
User Action:
Check the resource name specified on the request.
Reason:
This message is the final reply written in response to an SVCI command.
System Action:
None.
User Action:
None.
Reason:
The message is sent when a SET request fails for one of the selected resources.
rrrr is the resource type (for example, TRANS).
dddddddd is the resource name.
nnn is the response code returned by the CICS EXEC interface.
System Action:
Processing continues.
User Action:
The meaning of the response code depends on the command and resource being processed. Values can be found in the CICS/ESA System Programming Reference by referring to the related system command for the request.
Reason:
This message is written if a SET CONN ACQ or SET CONN REL is issued for an MRO connection. ACQ and REL are valid only with APPC connections. nnnn is the name of the MRO connection.
System Action:
The request is rejected.
User Action:
MRO connections cannot be set acquired or released.
Reason:
This message is written to the CICS system log by the SVCI abend handler. The abend handler is invoked when the SVCI or command transaction is abended by CICS. cccccccc is the CICS job name, and xxxx is the transaction abend code.
System Action:
Usually, the SVCI transaction attempts to restart. The command processors, however, will be terminated.
User Action:
Collect the transaction dump output, and report the problem to Technical Support.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |