|
|
|
CA XCOM Data Transport has a set of system parameters that govern its operation across all of its various interfaces. The CA XCOM Data Transport system parameters take effect as soon as CA XCOM Data Transport is started and, unless overridden, they remain in effect as long as CA XCOM Data Transport is active. These system parameters have historically been kept in the CA XCOM Data Transport Default Options Table. These parameters are now stored in a TYPE=CONFIG control library PDS member.
Important! A TYPE=CONFIG member is automatically created in the first data set in the XCOMCNTL DD concatenation the first time a Default Options Table is used, for which no TYPE=CONFIG member exists. Subsequent server initialization using the same DFLTAB or CONFIG name uses the TYPE=CONFIG member instead of the assembled Default Options Table.
When migrating from r11.5 or below, it is mandatory that the Default Options Table is reassembled before starting a CA XCOM Data Transport address space for the first time. Reassembling the table ensures that default values for any new Default Option Table parameters are included in the creation of the TYPE=CONFIG member. Failure to reassemble the Default Option Table results in the following error message:
XCOMM002IE DEFAULT OPTIONS TABLE SHOULD BE REASSEMBLED.
GEN-LEVEL/VERSION (xxxx-xxx) DOES NOT MATCH XCOMXFER (yyyy-yyy).
The CA XCOM Data Transport address space is then terminated.
Note: For descriptions of CA XCOM Data Transport system parameters, see the Configuration Parameters chapter in the CA XCOM Data Transport for z/OS Administration Guide.
This section contains the following topics:
This section describes the new PARM parameter.
Indicates the name of the TYPE=CONFIG control library member that is read and used by the CA XCOM Data Transport server.
Specifies the TYPE=CONFIG member XCOMDFLT.
Specifies the name of the TYPE=CONFIG member other than XCOMDFLT. This name can be up to eight alphanumeric characters long.
Notes:
Default: XCOMDFLT
Reason:
This message identifies the source of the parameters that follow as being the TYPE=CONFIG member read during the XCOM server startup. XXXXXXXX is replaced by the name of the PDS member that was specified on the CONFIG= EXEC parameter.
Action:
None
Reason:
This message identifies the source of the parameters that follow as being the EXEC statement PARM= field.
Action:
None
Reason:
A parameter value was parsed which was expected to be numeric, but non-numeric data was found.
Action:
Correct the parameter value by removing any non-numeric characters and resubmit the job.
Reason:
The numeric value parsed from the parameter is less than the minimum allowed for this numeric parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The numeric value parsed from the parameter is greater than the maximum allowed for this numeric parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The length of the value parsed from the parameter is greater than the maximum number of characters allowed for this parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The length of the value parsed from the parameter is less than the minimum number of characters allowed for this parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The value parsed from the parameter contains characters that are not allowed for this particular parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed format.
Reason:
The value parsed from the parameter does not match the keywords allowed to be specified for it.
Action:
Correct the parameter value by changing it to be a keyword from the list of possible options for this parameter.
Reason:
The keyword parameter specified in the record is not from the list of supported parameters which can be specified in a TYPE=CONFIG member.
Action:
Check the spelling of the keyword parameter and correct if necessary, or ensure that the parameter is in fact valid for CA XCOM.
Reason:
Severe errors were detected in the parameter records in the TYPE=CONFIG member such that initialization of the CA XCOM program being invoked cannot continue.
Action:
Correct the parameter errors noted prior to this message and resubmit the job.
Reason:
Moderate errors were detected in the parameter records in the TYPE=CONFIG member, however the PARSE_MODE option is set to "STRICT". As such, initialization of the CA XCOM program being invoked cannot continue.
Action:
Correct the parameter errors noted prior to this message and resubmit the job.
Reason:
The data set name or prefix specified in the parameter being processed has failed the validation checks implemented by the CA XCOM parameter parsing program. These checks enforce the data set naming conventions established by IBM for z/OS data set names.
Action:
Correct the data set name or prefix specification on the parameter statement and resubmit the job.
Reason:
The prior statement indicated it was being continued to the statement immediately preceding this message. However, the data contained in this parameter statement does not begin in the columns (2 – 16) which are required for second and subsequent continuation statements.
Action:
Check the starting column of this parameter statement and ensure that 1) continuation is desired, and 2) that the data in this statement begins in the correct column range required for continuation. Make any necessary corrections to the parameter statement and resubmit the job.
Reason:
The prior statement indicated it was being continued to the statement immediately preceding this message. However, the data contained in this parameter statement begins in column 1, which is not valid for a continuation statement.
Action:
Check the starting column of this parameter statement and ensure that 1) continuation is desired, and 2) that the data in this statement begins in the correct column range required for continuation. Make any necessary corrections to the parameter statement and resubmit the job.
Reason:
The prior statement indicated it was being continued to the next parameter statement. However, an end-of-file condition was raised before the continuation statement was read.
Action:
Ensure that the previous statement should have been flagged for continuation. If so, add a parameter statement to provide the continuation data that is expected. If not, remove the "+" from the prior parameter statement. Resubmit the job.
Reason:
Some configuration parameters require that the first character be Alphabetic (A-Z) or the characters "@", "#" or "$". The parameter being defined has that requirement, but the value being provided does not conform to it.
Action:
Ensure that the first character of the value (or of each data set name node in the case of a data set name or prefix) conforms to the restriction outlined above.
Reason:
The CA XCOM Data Transport SAVE console command was entered, but no member name was provided as a parameter.
Action:
Specify the name of the CONFIG member which is to be saved or replaced in the first XCOMCNTL data set.
Reason:
The CA XCOM Data Transport SAVE console command was entered along with a member name, but the parameter identified in the message is not recognized as being valid for the command.
Action:
Either enter the console command again without the parameter noted in the message, or correct it to be a valid option for the SAVE command.
Reason:
A CONFIG member with the name specified in the message is being created in the XCOMCNTL data set. The second, optional portion of this message is written if the member is being automatically created from an existing CA XCOM Data Transport Default Options Table, and includes the name and timestamp from when it was assembled.
Action:
None
Reason:
A SAVE command was entered for the module named in the message, but it already exists in the XCOMCNTL dataset. An existing CONFIG member can only be overwritten by adding the REPLACE optional keyword to the command syntax.
Action:
Verify that the member referenced in the message is the correct one, and either specify a different member name, or specify the REPLACE option to cause it to be overwritten.
Reason:
The CONFIG member named in the message is being overwritten with the system parameters currently in effect.
Action:
None
Reason:
The identified parameter was specified but the value will be ignored because the parameter has been deprecated.
Action:
Remove the identified deprecated parameter; otherwise the message can be ignored.
| Copyright © 2012 CA. All rights reserved. |
|