|
|
|
CA XCOM Data Transport has implemented a means of generically scheduling to a group of servers. This was introduced as the XCOMPLEX. The PLEXQ facility is the redesign of that facility to provide enhanced performance and system resource utilization.
Release 11.6 of CA XCOM Data Transport will provide this enhanced PLEXQ capability.
IBM SYSPLEX Signaling Services are the means of communication in the new PLEXQ architecture. Batch XCOMJOB utility jobs connect to a PLEXQ group, to which CA XCOM Data Transport servers are already joined. The XCOMJOB utility communicates with the member servers in the PLEXQ to manage transfer workload and activity.
The PLEXQ brings with it a new protocol which may be substituted for SNA and TCP/IP when performing meta-transfers between XCOMJOB and XCOM servers. A PLEXQ group can be used to communicate with one or many servers, thus it can be used as an alternate protocol for performing transfer scheduling and inquiry for even an individual server. The advantage of using the PLEXQ is that it uses less storage and requires fewer system resources than when an SNA or TCP/IP connection is used.
PLEXQ connectivity can be used for each of the following XCOMJOB request types:
Tracing has been enhanced in CA XCOM Data Transport to show the exchange of data between members of a PLEXQ group. Entries in the TRACEDD output dataset are created to show the state of communications as well dumps of buffer content to facilitate problem determination related to PLEXQ activities.
This section contains the following topics:
Allowing TYPE=OPER (Operator) Requests from ISPF to the PLEXQ
This section describes the new PARM and Configuration parameter value allowed by the CA XCOM Data Transport Server and XCOMJOB meta-transfer jobs for enabling PLEXQ support.
Specify the name of the PLEXQ group to which the CA XCOM Data Transport server (XCOMXFER) is to connect. This parameter only applies to the server.
Specify the name of the PLEXQ group to which the XCOMJOB batch utility is to connect. This parameter only applies to XCOMJOB executions using TYPEs other than EXECUTE. There must be a server already connected to the PLEXQ group in order for the request to complete successfully.
This section describes the new modify commands to manage and monitor activities within PLEXQ member servers.
Allows for the display of task levels in servers which are members of the same PLEXQ as the server from which the command is issued.
Note: This STAT command is analogous to the STAT command which previously could only be issued from an XCOMPLEX ADMIN server. The PLEXQ STAT command can be entered from any peer server in the PLEXQ group.
F XCOM,STAT
The use of the STAT command requires that the command issuer's security authorization contain READ access to the following resource specification for CLASS(OPERCMDS):
XCOM.applsec.STAT
Allows for the display of locally initiated transfers in all members of the same PLEXQ as the server from which the command is issued.
Note: This XSHOW command is analogous to the XSHOW command which previously could only be issued from an XCOMPLEX ADMIN server. The PLEXQ XSHOW command can be entered from any peer server in the PLEXQ group.
F XCOM,XSHOW
The use of the XSHOW command requires that the command issuer's security authorization contain READ access to the following resource specification for CLASS(OPERCMDS):
XCOM.applsec.XSHOW
Allows for the display of remotely initiated transfers in all members of the same PLEXQ as the server from which the command is issued.
Note: This XRSHOW command is analogous to the XRSHOW command which previously could only be issued from an XCOMPLEX ADMIN server. The PLEXQ XRSHOW command can be entered from any peer server in the PLEXQ group.
F XCOM,XRSHOW
The use of the XRSHOW command requires that the command issuer's security authorization contain READ access to the following resource specification for CLASS(OPERCMDS):
XCOM.applsec.XRSHOW
Reason:
An IBM Signaling Services macro has terminated with a return code indicating that the PLEXQ GROUP has been damaged.
Action:
Terminate all CA XCOM servers and batch utilities that are connected to the PLEXQ group and attempt to restart them. In the event that this condition should occur, the underlying cause of the failure should be investigated. This is a system environmental error and a solution should be pursued through IBM support.
Reason:
This message indicates that this CA XCOM program has connected to the PLEXQ GROUP identified in the message. Variable substitution in the message text is as follows:
yyyyyyyy = the name of the PLEXQ group to which this program connected.
zzzzzzzz = the name by which this program is know in the PLEXQ group.
Action:
None
Reason:
This message indicates that this CA XCOM program has disconnected from the PLEXQ GROUP identified in the message. Variable substitution in the message text is as follows:
yyyyyyyy = the name of the PLEXQ group to which this program connected.
zzzzzzzz = the name by which this program is know in the PLEXQ group.
Action:
None
Reason:
This message indicates that another CA XCOM program has connected to the PLEXQ GROUP identified in the message, and to which the region which issued the message was already connected. Variable substitution in the message text is as follows:
wwwwwwww = the name of the system where the connector is running.
xxxxxxxx = the name of the job or started task which connected.
yyyyyyyy = the name of the PLEXQ group to which the program connected.
zzzzzzzz = the name by which the program is know in the PLEXQ group.
Action:
None
Reason:
This message indicates that another CA XCOM program has disconnected from the PLEXQ GROUP identified in the message. The region issuing this message is connected to the named PLEXQ GROUP. Variable substitution in the message text is as follows:
xxxxxxxx = the name of the system where the disconnector is running.
yyyyyyyy = the name of the job or started task which disconnected.
zzzzzzzz = the name of the PLEXQ group to which the program connected.
Action:
None
Reason:
An XCOM server attempted to connect to a PLEXQ where the other XCOM servers in the PLEX are at a different release of CA XCOM Data Transport. The PLEXQ only allows connections by servers running the same release of CA XCOM Data Transport. XXXXXX is the type of CA XCOM Data Transport job, SERVER, JOB or, ADMIN. YYYYYYYY specifies the name of the PLEXQ group that the connection is attempted to.
Action:
None required. The XCOM Server continues to run as a stand-alone server.
Reason:
This message indicates that the macro specified in the message has completed with a non-zero return code, indicating that a failure has occurred. Variable substitution in the message text is as follows:
xxxxxxxx = the name of the macro which failed
yyyyyyyy = the return code from the failing macro call
zzzzzzzz = the reason sub-code from the failing macro call
Action:
Locate the RETURN and REASON codes for the appropriate macro in the IBM z/OS documentation and follow the instructions for the specific error code listed there.
Reason:
This message indicates that an expected response to a prior request was not received by the PLEXQ protocol management module within the timeout limit.
Action:
Ensure that the partner region receiving the request is still operational. Increase the TIMEOUT parameter for the local region if the partner region is still functional. If all regions are still operational, gather all output from the requesting CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ message which was received contains an invalid message type identifier. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which is missing a critical control block address. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which has an invalid address for a critical control block. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which is missing a critical control block address. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which has an invalid address for a critical control block. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which is missing a critical control block address. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which has an invalid address for a critical control block. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
There is not enough available virtual storage in the CA XCOM region to invoke the transaction program needed to service the request.
Action:
Do one or more of the following:
Reason:
The address of an ECB needed to communicate with another task within the CA XCOM region is not valid. This indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A STAT, USTAT, XRSHOW, or XSHOW command was entered but the PLEXQ group is not active.
Action:
None.
Reason:
The task within the CA XCOM region which processes PLEXQ messages is being started or is stopping.
Action:
None
Reason:
The command byte in the internal PLEXQ request buffer is not valid.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
An error occurred which caused the request identified by xxxxxxxx to not be completed successfully.
Action:
Review the XCOMLOG and other SYSOUT messages from the CA XCOM invocation looking for other error messages relating to the failed request. If insufficient information was displayed to identify the problem, gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
An attempt to acquire storage to use as a buffer for a PLEXQ operation has failed.
Action:
The most common cause of this message is a shortage of virtual storage available within the CA XCOM address space. If possible, increase the REGION JCL parameter for the execution of the program. If there is sufficient storage, check the CA XCOM SYSOUT for other messages relating to errors that may have occurred during the execution of the CA XCOM program.
Reason:
The macro call issued to connect to the SYSPLEX Signaling Services Group (named by xxxxxxxx) has received a return code indicating that the connection attempt was unsuccessful.
Action:
Examine the XCOMLOG and SYSOUT from the CA XCOM region to locate any additional messages relating to the PLEXQ connection. Take the action(s) indicated for any such messages.
Reason:
The LSEXPAND macro is used to expand the available stack area for program use within an address space. This macro call has failed with the return code indicated by xxxxxxxx.
Action:
Review the documentation for the LSEXPAND system service and follow the instructions for the return code that was received. This is likely a system environmental error.
Reason:
The XCOMJOB batch utility was invoked specifying a STCPLEXQ parameter of xxxxxxxx, but no servers were found connected to SYSPLEX Signaling Services using that group name.
Action:
Verify that the spelling of the group name on the STCPLEXQ EXEC PARM for the XCOMJOB utility is correct. If the group name is spelled correctly on the STCPLEXQ EXEC PARM, verify that a CA XCOM server (XCOMXFER) has been started, connected and is still active using the specified PLEXQ group name.
To allow users to perform TYPE=OPER transfers of PDSE program libraries, add XCOMPLEX to the AUTHPGM and the AUTHTSF tables of IKJTSO00 module in SYS1.PARMLIB. The CA XCOM Data Transport libraries used in your CLIST for the CA XCOM Data Transport ISPF interface must all be APF authorized also.
You can also refresh the TSO library using the TSO UPDATE PARMLIB(00) member. For more information, see the IBM TSO/E Customization manual.
| Copyright © 2012 CA. All rights reserved. |
|