The following messages could appear on the HCI job log output during execution. These messages are issued by the CSS TP servicing Host Explorer and Xpediter/Eclipse users.
Each of the messages contains a message ID starting with CX and is followed by a 4-digit number representing the task number. The task number can be used to group messages issued by the various TPs in execution.
| |
|---|
| command received from user ID Explanation: The SSAS received an operator console command from the specified user ID.
System Action: None. |
| Journal task not active; restart SSAS to activate
Explanation: Journaling could not start for the SSAS because the journal task is not active. The journal task can fail to start if it cannot allocate or open the journal datasets, or if no SSAS journal datasets were specified in TP Configuration File. Processing continues normally, but without journaling.
System Action: Verify the journal dataset exists, and that it has universal update access and shutdown the SSAS with the MVS STOP command. It will restart automatically on the next request from a client user. |
| Request not recognized; input ignored
Explanation: A MVS MODIFY command was issued to the SSAS, but the command was not recognized. Processing continues.
System Action: Reenter the command with the proper input parameters. |
| CXTRACE request active for user userid
Explanation: A MVS MODIFY command was issued to the SSAS to start a CXTRACE at the request of BMC Support.
System Action: None |
| CXTRACE request ignored; currently active for user userid
Explanation: A MVS MODIFY command was issued to the SSAS to start a CXTRACE but the trace was already active. Processing continues with CXTRACE active.
System Action: None |
| CXTRACE now inactive
Explanation: A MVS MODIFY command was issued to the SSAS to stop an active CXTRACE.
System Action: None |
| ssasname initialization complete
Explanation: The SSAS has successfully started and is ready for use. The ssasname is the name specified in the TP Configuration File member.
System Action: None. |
| ssasname is running APF-authorized
Explanation: The SSAS is operating with APF-Authorization. The SSAS does not currently require APF-authorization and some routines may not execute properly in this environment.
System Action: None, but it is recommended that SSAS run non-authorized. |
| Journal now recording to dataset name
Explanation: The SSAS journal dataset successfully.
System Action: None. |
| Journal dataset name closed
Explanation: The SSAS journal dataset has been closed successfully.
System Action: None. |
| No JOURNAL datasets defined
Explanation: No SSAS journal datasets were defined in the TP Configuration File member. Processing continues without journaling.
System Action: None. |
| Could not allocate dataset name,
Explanation: A SSAS journal dataset specified in TP Configuration File member could not be allocated. This message is followed by CXASJRN044S. A user abend 0027 is issued, but processing continues without journaling.
System Action: Verify the journal dataset exists, and that it has universal update access. |
| Could not open dataset name,
Explanation: A SSAS journal dataset specified in TP Configuration File member could not be opened. This message is followed by CXASJRN045I. A user abend 0027 is issued, but processing continues without journaling.
System Action: Verify the journal dataset exists, and that it has universal update access. |
| Journal write RPL error X''xx''
Explanation: An RPL occurred attempting to write a journal record. The RPL error code is from the VSAM PUT macro. Processing continues normally, but without journaling.
System Action: Reallocating the SSAS journal datasets and restarting the SSAS may help. If the error persists, contact BMC Support. |
| Allocation S99ERROR=X''xx''
Explanation: A SSAS journal dataset specified in TP Configuration File member could not be allocated. This message is preceded by CXASJRN026S. A user abend 0027 is issued, but processing continues without journaling. The S99ERROR value specified the dynamic allocation error code.
System Action: Verify the journal dataset exists, and that it has universal update access. |
| Journal task ended
Explanation: SSAS is unable to start journaling. The journal task is terminated with a user 0027 abend, and processing continues without journaling.
System Action: None. |
| Term RC=% FDBK=% Reason=% z=% mms
Explanation: A SSAS subtask has terminated. The last return code and reason code processed while the task was executing is shown in the FDBK= and Reason= fields. The z= field shows the amount of zIIP processing time consumed by the TP subtask during execution, in microseconds (if zIIP processing is enabled, otherwise this value is 0). The z= value will always be 0 for SSAS task. Severity: I
System Action: None. The FDBK and Reason values are available through customer support. The RC= value is indicative only that an error occurred, and does not contain a useful value. |
| Req = code function userid
Explanation: A diagnostic aid message that indicates the current SSAS function being requested by a client user. The code is the function code output by the XML parser and the function value is high level name of the function to be performed. This message is only informational.
System Action: None. |
| Abend abend-code
Explanation: During SSAS subtask execution, an abend was encountered. An abend dump is produced and is available in the HCI sysout with a ddname of TPnnnn where nnnn is the task number of this TP identified in the message.
System Action: Most abends can be ignored unless they persist. Contact BMC Support if necessary. |
| Open failed on configuration dataset
Explanation: The CSS TP Configuration File dataset could not be opened.
System Action: Verify that the dataset is created and the configuration member exists. Verify that the dataset has universal READ access. Verify that the TPCONFIG DD statement exists in the HCI start-up JCL stream and that it specifies this dataset. |
| Configuration parameter cannot begin in column 1
Explanation: An unexpected character was found in column 1 of the configuration member.
System Action: Column 1 of the configuration member can only contain an asterisk character, indicating a comment, or a blank character. All parameters specified in the member must begin in any other column. |
| Error parsing configuration parameter in record x
Explanation: An unexpected error was encountered examining the parameters specified in the configuration member. Severity: S
System Action: Each parameter statement must begin after column 1, and all subsequent parameters on the line must be separated by one or more blanks. Other than the blank separation, the record is free form and data can begin in any column except column 1. This message is followed by CXTPCFG004W which shows a portion of the failing record. |
| RECORD=" record text "
Explanation: This message follows a prior message indicating an error processing the configuration member. The record text shows a portion of the failing record. Severity: S
System Action: Correct the failing record using the syntax of the parameter as described in the configuration steps of the Installation Guide. |
| Blank configuration parameter ignored
Explanation: A blank configuration parameter was encountered and skipped examining the parameters specified in the configuration member. Severity: I
System Action: Check the parameter against those listed in the Installation Guide and specify a value if one is desired. This message is followed by CXTPCFG006I which shows a portion of the blank record. |
| RECORD = “record text”
Explanation: This message follows a prior message indicating a blank configuration parameter. The record text shows a portion of the blanked parameter record. Severity: I
System Action: Correct the blank configuration parameter if a value is desired. |
| Term RC=% FDBK=% Reason=% z=% mms
Explanation: A CSS TP subtask has terminated. The last return code and reason code processed while the task was executing is shown in the FDBK= and Reason= fields. The z= field shows the amount of zIIP processing time consumed by the TP subtask during execution, in microseconds (if zIIP processing is enabled, otherwise this value is 0).
System Action: None. |
| SLSE Status=xxxxxxxx CPIC-RC=yy
Explanation: A TP user is attempting to logon, but the logon attempt could not be verified. The status codes (in hex) are: | |
|---|
| | | | | | | | | | | | | | | | | | | | | | | | | | User ID not valid for group | | | User ID revoked from group | | | Unspecified error returned from HCI CW_SLSE |
System Action: Retry the logon attempt or contact your on site security administrator. For reason code 0000000A, contact BMC Support and provide the reason code and CPIC-RC value in the message.
|
| Init tpname Hxxxxxxxx
Explanation: A CSS TP has been initiated. This message is issued instantly upon contact of the HCI by a client user. No data has yet been received or sent, this only indicates contact has occurred. The name of the TP is displayed as well as the TCB address of the new subtask in the Hxxxxxxx field.
System Action: None. |
| XML tag error X''xx'', tag=<tttt>
Explanation: A message was received from the client connection but during processing of the message an XML parsing error was encountered.
System Action: This error can sometimes be encountered if a connection was dropped and reestablished. But if the error persists or occurs repeatedly when a client user is attempting to perform a valid function, contact BMC Support. This error is usually identified in Host Explorer as RC=160, Reason=xx where the reason code is the same one in the message above. |
| Abend abend-code
Explanation: During TP subtask execution, an abend was encountered. An abend dump is produced and is available in the HCI sysout with a ddname of TPnnnn where nnnn is the task number of this TP identified in the message.
System Action: Most abends can be ignored unless they persist. Contact BMC Support if necessary. |
| Hello from ip-address userid
Explanation: The client user was successfully logged on and the TP subtask is executing under the security profile for the userid indicated in the message. In some cases a userid value might not be shown; in this instance (such as a CICS debugging session launch by Xpediter/Eclipse), the security profile will be later established by CICS.
System Action: None. |
| Req = code function
Explanation: A diagnostic aid message that indicates the current function being requested by a client user. The code is the function code output by the XML parser and the function value is high level name of the function to be performed. This message is only informational. |
| Open VTAM ACB failure - ACBERROR=X''xx', APPLID=aaaaaaaa
Explanation: During an Xpediter/Eclipse interactive TSO debugging session launch, the VTAM ACB could not be opened. This is accompanied by RC=164,Reason=XX, which is the ACB ERROR field value.
System Action: Probable specification error of VTAM APPL definitions. Several possible causes exist: "APPL definition not defined" "APPL not specified in the TP configuration file "APPL in use by another application "APPL requires a password (no APPL password support existing in Xpediter/Eclipse) "APPL access restricted by local security rules Look up the ACBERROR code in the reference below to determine the cause. If the cause cannot be corrected locally, contact BMC Support and provide the reason code. Common reason codes and their meanings: 14 - Insufficient storage to open the ACB 24 - User is not authorized to use the APPL 52 - VTAM is shutting down 58 - The APPL is already in use by another program or user 5A - The APPL was not defined to VTAM Reference: IBM’s z/OS Communications Server SNA Programming (see Conventions and Descriptions of VTAM macroinstructions). After the description of the OPEN macro a list of possible return codes is listed. The ACBERROR code xx is the OPEN return code. |
| RPL error - R15=xx,R0=xx,FDBK2=xx,O=xx,C=xx,N=xx
Explanation: During an Xpediter/Eclipse debugging session with TSO, a communications error occurred between the TP and VTAM.
System Action: This is an internal error. Contact BMC Support and provide the reason code. |
| Member mmmmmmmm not found in dataset DD TPCONFIG (FIND RC=04)
Explanation: When attempting to process the TP Configuration File member, the member could not be located.
System Action: Verify that the dataset is created and the configuration member exists. Verify that the dataset has universal READ access. Verify that the TPCONFIG DD statement exists in the HCI start-up JCL stream and that it specifies this dataset. Verify that the member name is identical to the name of the TP (TPNAME parameter value on the HCICNPCB macro in the HCI Configuration). |
| FIND member mmmmmmmm failed in DD TPCONFIG, R15=xx, R0=xx
Explanation: When attempting to process the TP Configuration File member, an error occurred trying to locate the member.
System Action: This message usually indicates some type of I/O error when trying to read a PDS directory. The R15 and R0 values are the return and reason codes from the FIND macro. Contact BMC Support for assistance. |
| Configuration file % successfully processed
Explanation: The TP Configuration File member was successfully processed and is now active.
System Action: None. |
| Additional JOURNAL datasets ignored (3 max)
Explanation: In the TP Configuration file member, more than three JOURNAL statements are specified. The maximum number of JOURNAL statements that can be specified is three.
System Action: Remove the extra JOURNAL statements from the configuration file member and refresh the configuration using the TPAdmin utility or restart the HCI. |
| This HCI is not at the required maintenance level to support CXTPCDE037W debugging with Xpediter/Eclipse.
Explanation: A diagnostic aid message that indicates the HCI hosting the CSS TP is not at the correct maintenance level to allow debugging with Xpediter/Eclipse.
System Action: Ensure the latest Compuware maintenance is applied to HCI and CSS. Then restart the HCI and retry the debugging session. |
| operation with Host Explorer.
Explanation: A diagnostic aid message that indicates the HCI hosting the CSS TP is not at the correct maintenance level to allow operation with all parts of Host Explorer.
System Action: Ensure the latest Compuware maintenance is applied to HCI and CSS. Then restart the HCI and retry the connection. |
| IP=ip address, Port=port, TCPNAME=tcp/ip stack name
Explanation: An Xpediter/Eclipse request to launch a CICS debugging session is showing the IP address and port number of the desired CICS. The TCP/IP stack name being used is displayed. The stack name should be the TCPNAME value specified in the HCI configuration's HCICNAMB macro.
System Action: None. The IP address displayed in the message must be the same as the z/OS system that the CICS region is executing, or the connection will not be successful. |
| tranid RS=xx, CLID=cics client id
Explanation: An Xpediter/Eclipse request to launch a CICS debugging session is showing the CICS transaction ID specified in the TP Configuration File. This information is only for diagnostic purposes when connection failures occur.
System Action: None. |
| Launch RC=xx FDBK=xxx Reason=xx
Explanation: An Xpediter/Eclipse request to launch a CICS or TSO based debugging session is showing the return code and reason codes, if any, issued by the launch sequence.
System Action: None. |
| Launch RC=xx FDBK=xxx Reason=xx
Explanation: An Xpediter/Eclipse request to launch a CICS or TSO based debugging session is showing the return code and reason codes, if any, issued by the launch sequence. This information is only for diagnostic purposes when connection failures occur.
System Action: None. |
| TSO=tttttttt APPL=aaaaaaaa PROC=pppppppp SIZE=ssss
Explanation: An Xpediter/Eclipse request to launch a TSO based debugging session is showing the TSO APPLID specified in the TP Configuration File, the selected user APPLID also from the APPL list in the TP Configuration File, the TSO JCL procedure and region size specified by the Xpediter/Eclipse user. This information is only for diagnostic purposes when connection failures occur.
System Action: None. |
| Ping from ipaddress
Explanation: Topaz Mainframe support was pinged to see if it was active.
System Action: None |
| zIIP parameter must specify either Y or N
Explanation: The zIIP parameter within the TP Configuration File's LOCAL statement must specify a value of Y or N, or not be coded (blank).
System Action: Correct the zIIP value coded on the LOCAL statement of the TP Configuration File member. |
| Values on ENABLE record must specify Y or N
Explanation: The values coded for an ENABLE statement within the TP Configuration File must specify a value of Y or N.
System Action: Correct the ENABLE values coded on the that statement within the TP Configuration File member. |
| EMCS Console tpname active CXTPSMC048I EMCS Console tpname inactive
Explanation: The extended MCS console for the TP has become active or inactive. This message is only informational. These messages may be accompanied by system messages IEA630I or IEA631I.
System Action: None. |
| EMCS console failed initialization, RC/RS=rr/ss
Explanation: The extended MCS console for the TP has failed its initialization. Job notification messages cannot be recorded. Severity: W
System Action: This error may be corrected by restarting HCI. However, if the error persists, contact BMC Support for assistance. The RC/RS values are the return and reason codes from the MCSOPER macro. This macro is documented in the z/OS MVS Authorized Assembler Services Reference SA22-7609. See to the MCSOPER macro. |
| NOTIFY must specify Y or N and a purge duration range of 0-999
Explanation: The NOTIFY statement in the TP Configuration File must specify a Y or N value indicating whether job notifications are to be enabled. The purge duration value specifies how many days the job notification data can be queued up for delivery before it is deleted because of non-delivery.
System Action: Specify Y or N after the NOTIFY keyword, and a value between 0 and 999 for the purge duration. The purge duration is in number of days. A purge duration of zero indicates no purging will occur for non-deliverable messages. |
| EMCS console message retrieval failed, RC/RS=rr/ss
Explanation: The extended MCS console for the TP was unable to continue searching for job notification messages.
System Action: This error may be corrected by stopping the TP's EMCS console via the TPAdmin utility and then restarting it, or by restarting HCI. However, if the error persists, contact BMC Support for assistance. The RC/RS values are the return and reason codes from the MCSOPMSG macro. This macro is documented in the z/OS MVS Authorized Assembler Services Reference SA22-7609. See to the MCSOPMSG macro. |
| ACCOUNT=account number
Explanation: The account number used for a TSO-based debug session is displayed for diagnostic purposes. This message is purely informational and might be used if TSO-based debug sessions are not correctly starting.
System Action: None. |
| message text
Explanation: If an unexpected message is issued by TSO or security software during the logon process that preceeds a TSO-based debugging session, the unexpected message text will be displayed. Severity: S
System Action: The message text is used to assist in diagnosis of debugging start-up failures with the assistance of BMC Support. |
| CXTPMSGS must specify FULL, QUIET, or NONE.
Explanation: The CXTPMSGS statement within the TP Configuration File member must be coded with one of the options being FULL, QUIET, or NONE, but an unexpected value was found. Severity: S
System Action: Correct the CXTPMSGS statement by specifying the correct option. |
| TP is not running APF-authorized
Explanation: The CSS TP requires APF-authorization to perform its functions. APF-authorization is a documented requirement.
System Action: Please ensure that the COMPWARE.MLCXnnn.SLCXAUTH library is properly APF-authorized, and that the other libraries in the associated STEPLIB concatenation are also APF-authorized so as not to lose APF-authorization for all datasets. |
| FXSERVER module could not be loaded CXTPFXV057S File-AID SXVJAUTH dataset missing from STEPLIB DD
Explanation: A load failed for the module FXSERVER. This usually means that the File-AID common authorized library is not in the STEPLIB DD concatenation of the TP started-task procedure named by the STASK statement in the TP Configuration File. These messages appear in the job log of the started-task.
System Action: If File-AID Data Editor is to be used by Topaz Workbench , specify the File-AID dataset's as specified in the sample procedure member CXSS0000 in COMPWARE.MLCXnnn.SLCXCNTL. If File-AID Data Editor is not to be used, this error can be ignored; it does not affect Topaz Workbench operation. FDBK code 793 Reason=08060004 is issued along with these messages. |
| DSNHLQ must contain characters A-Z, 0-9, #,@,$ only
Explanation: A high level qualifier was specified via the DSNHLQ statement in the TP Configuration File. The qualifier is invalid and does not consist of the valid characters for specifying dataset names.
System Action: Correct the DSNHLQ parameter to specify only the characters consisting of A through Z, 0 through 9, #, @, or $ |
| DSNHLQ must start with a non-numeric character
Explanation: A high level qualifier was specified via the DSNHLQ statement in the TP Configuration File. The qualifier is invalid and does not begin with a non-numeric character as required for specifying dataset names.
System Action: Correct the DSNHLQ parameter to specify only the characters consisting of A through Z, or #, @, or $ as the first character of the qualifier. |
| INACTIVITY time out value range must be 0-32767
Explanation: The time out minutes value for the INACTIVITY statement is the first numeric parameter of two parameters on this statement. This value must be in a range of zero to 32767. A zero value indicates that no connections are to be terminated due to inactivity.
System Action: Correct the first INACTIVITY parameter to specify a time out value in minutes in the range 0-32767. |
| SYSCMD/SYSLOG must specify Y or N and a rule of SYSTEM, SDSF, or IOFx
Explanation: The SYSCMD/SYSLOG configuration parameter was not correctly specified.
System Action: Fix the configuration parameter in accordance with the requirements in the ECC Advanced Configuration Guide. |
| TP control task active TP control task has ended
Explanation: These messages simply indicate that the TP control task has started or has ended. They will be issued when the first TP starts up, and when the HCI is shut down. System Action: None. |
| NOTIFYONLY must specify one of ALL or LOCAL
Explanation: The NOTIFYONLY statement parameter is incorrectly specified. The parameter values must be specified as ALL or LOCAL.
System Action: Correct the NOTIFYONLY parameter to specify ALL or LOCAL. Explanation: CXTPFXV056S FXSERVER module could not be loaded; |
| FXSERVER module could not be loaded; CREDENTIALS must specify ENABLE or DISABLE.
Explanation: The CREDENTIALS configuration parameter was not correctly specified. Its value must be either ENABLE or DISABLE.
System Action: Fix the configuration parameter in accordance with the requirements in the ECC Advanced Configuration Guide. |
| READTIMEOUT value range must be 0-999
Explanation: The READTIMEOUT configuration parameter was specified with a value outside of the allowed 0-999 seconds range.
System Action: Fix the configuration parameter in accordance with the requirements in the ECC Advanced Configuration Guide. |
| Error calling common parmlib RC=xx Reason=xx
Explanation: Topaz Mainframe support's parameter retrieval failed with the return code and reason coded specified in the message.
System Action: If RC=8, Reason=4 - the PARMLIB member was not found. Look in the CW parameter dataset if the member is present. If not, add the member. Otherwise contact BMC Support with the return and reason codes. |
| Port not found in parmlib member
Explanation: A port was not specified in the parmlib member of this HCI.
System Action: Specify a port number in the parmlib member for this HCI in accordance with the ECC Advanced Configuration Guide. |
| CMSC retrieved memname from DSN mm
Explanation: The parmlib member memname was retrieved by the CMSC from DSN mm and is in use for this HCI.
System Action: None. |
| Invalid parm=parm
Explanation: A parm specified in the used parmlib member is invalid. A snippet of the invalid parm record is given in the message.
System Action: Fix the invalid parm in accordance with the ECC Advanced Configuration Guide. |
| Storage obtain failed for CMSC routine
Explanation: The HCI failed to obtain storage as part of parmlib member processing.
System Action: Increase the region size of the HCI. If the problem persists, contact BMC Support. |
| SYSOUT must specify DEFAULT or BY-USERID
Explanation: The CSS TP configuration parameter SYSOUT was not correctly specified. Its value must be either DEFAULT or USERID.
System Action: Fix the SYSOUT configuration parameter in accordance with the requirements in the ECC Advanced Configuration Guide. |
| ISPW connect at IP=ipaddress, Port=portnum, TCPNAME=tcpname
Explanation: A successful ISPW connection has been made to the ISPW CM at the IP address and port shown over the named TCP/IP stack.
System Action: None. |
| ISPW communications error FUNC=tcpipfunc R/C=nn RETCODE=mm ERRNO=xx
Explanation: A TCP/IP error occurred during an ISPW communications request. tcpipfunc contains the request type that failed, nn contains the return code from TCP/IP, mm contains the error code from TCP/IP, and xx contains the return code from the routine using TCP/IP (may not be specified).
System Action: Ensure the ISPW CM is up and running. Consult the IBM IP Sockets Programming Guide for more information on the TCP/IP return code and error number for possible site TCP/IP issue. If issues persist, contact BMC Support. |
| Error adding task-level resource manager. RESMGR RETCODE =mm
Explanation: An attempt to add a resource manager failed. The return code from the resource manager is provided.
System Action: Contact BMC Support with the resource manager return code. |
| Error loading module modnam. RC=mm. RSN=nn..
Explanation: When Total Test support was attempting to load module modnam, an abend occurred. mm and nn respectively contain the abend code and associated abend reason code.
System Action: Depends on the abend code. Ensure that the load module exists and is in the same load library as CXTPMAIN. If this problem persists, contact BMC Support. |
| Unable to locate Total Test PARMLIB member
Explanation: Topaz Mainframe support was unable to locate your Total Test PARMLIB member.
System Action: Check your parmlib and ensure that the Total Test parmlib member exists. If it doesn't, add the member. If the issue persists, contact BMC Support. |
| Error in Total Test interface
Explanation: A general error occurred within Total Test support. A feedback code of 2002 with a reason code has been passed to the user that encountered the error.
System Action: If this issue persists, contact BMC Support with the reason code given to the user. |
| HCI hciname USER userid entered z/OS command command
Explanation: User with ID userid issued command through the HCI with jobname hciname using the z/OS Console in Topaz.
System Action: None. If the command was truncated, the snippet provided in this message can be linked up with the full command which will be closely beneath this message in the M. |