|
|
|
Reason:
The requested action requires a transmission definition name but none was entered.
System Action:
None.
User Action:
Provide the transmission definition name and retry.
Reason:
The requested action requires an initiator destination name but one was not entered.
System Action:
None.
User Action:
Provide the initiator destination name and retry.
Reason:
The requested action requires a transmission definition name but none was entered.
System Action:
None.
User Action:
Provide the transmission definition name and retry.
Reason:
There are no transmission definitions that match the requested name mask ( P1 ).
System Action:
None.
User Action:
None.
Reason:
The transmission definition ( P1 ) does not exist. The definition may have been deleted by another user.
System Action:
None.
User Action:
If this message occurs when selecting an action on a list of transmission definitions, use the REFRESH action to refresh the list.
Reason:
A transmission definition ( P1 ) was successfully actioned. The type of action ( P1 is added, updated, deleted) is shown.
System Action:
None.
User Action:
None.
Reason:
A transmission definition ( P1 ) was not added. There is already a definition of the same name. This condition usually only occurs if multiple users try to add the same definition name simultaneously.
System Action:
None.
User Action:
Specify a different name and retry.
Reason:
An attempt to open the data set that contains FTS definitions (the VFS) failed for the indicated reason ( P1 ).
System Action:
None.
User Action:
Use the reason to resolve the problem.
Reason:
The requested action requires a transmission destination name but none was entered.
System Action:
None.
User Action:
Provide the transmission destination name and retry.
Reason:
There are no transmission requests for the requested destination/origin mask ( P2 ) for the indicated direction ( P1 is Inbound or Outbound).
System Action:
None.
User Action:
None.
Reason:
The transmission definition ( P2 ) does not exist in the indicated direction ( P1 is Inbound or Outbound). The request may have have been deleted by another user.
System Action:
None.
User Action:
If this message occurs when selecting an action on a list of transmission requests, use the REFRESH action to refresh the list.
Reason:
A transmission request ( P1 ) was successfully actioned. The type of action ( P1 is added, updated, deleted) is shown.
System Action:
None.
User Action:
None.
Reason:
The requested action requires an initiator destination name but one was not entered.
System Action:
None.
User Action:
Provide the initiator destination name and retry.
Reason:
There are no initiator destination that match the requested name mask ( P1 ).
System Action:
None.
User Action:
None.
Reason:
The initiator destination ( P1 ) does not exist. The destination may have been deleted by another user.
System Action:
None.
User Action:
If this message occurs when selecting an action on a list of initiator destinations, use the REFRESH action to refresh the list.
Reason:
An initiator destination ( P1 ) was successfully actioned. The type of action ( P1 is added, updated, deleted) is shown.
System Action:
None.
User Action:
None.
Reason:
A initiator destination ( P1 ) was not added. A destination of the same name already exists. This condition usually occurs only if multiple users try to add the same destinition name simultaneously.
System Action:
None.
User Action:
Specify a different name and retry.
Reason:
No initiator destinations match the specified selection criteria.
System Action:
None.
User Action:
None.
Reason:
The Service Class specifies a set of single-character class values that must be unique. A class value ( P1 ) is duplicated.
System Action:
None.
User Action:
Correct the list of classes and retry.
Reason:
A request to define a started initiator is not valid until at least one Service Class is defined.
System Action:
None.
User Action:
Do one of the following:
- Change the value to No
- Define the Service Classes
Reason:
You are not authorized to perform the requested function.
System Action:
The request is rejected.
User Action:
Contact your systems administrator if the function is required.
For CA SOLVE:FTS security requirements, see the following manuals:
Reason:
You are not authorized to perform the requested function.
System Action:
The request is rejected.
User Action:
Contact your systems administrator if the function is required.
For CA SOLVE:FTS security requirements, see the following manuals:
Reason:
The request to access the transmission request or definition has been rejected because the user's access mask P2 does not allow access to the specified definition ( P1 is System or Private).
System Action:
The request is rejected.
User Action:
None.
Reason:
There are no transmission definitions that match the specified selection criteria.
System Action:
None.
User Action:
None.
Reason:
You must specify either a data set name or a DD name (but not both).
System Action:
None.
User Action:
Specify the data set name or DD name and retry.
Reason:
You must specify either a data set name or a DD name (but not both).
System Action:
None.
User Action:
Erase either the data set name or DD name and retry.
Reason:
You have tried to save a transmission definition record but have not specified any details for the "TO" data set.
System Action:
None.
User Action:
Use the ToFile or ToSYSOUT commands to display the requisite "TO" detail panel and enter the details before saving the definition.
Reason:
The transmission definition specifies a "TO" data set name of SYSOUT indicating that the target is SYSOUT. However, the SYSOUT class has not been specified.
System Action:
None.
User Action:
If the intention is to create a SYSOUT file, you must specify the SYSOUT details on the "To SYSOUT" panel. If you want to create a file, you must choose a different "To" data set name.
Reason:
The P1 field may be specified only for system definitions.
System Action:
None.
User Action:
Erase the field in error.
Reason:
You must specify a volume serial number or a device type (or both) for a new data set (Disposition=NEW).
System Action:
None.
User Action:
Specify the Volume serial number or device type (or both), and retry.
Reason:
You specified some but not all of the allocation details for the new data set.
The space allocation details for a new data set (Disposition=NEW) are specified using the following fields:
- Space type
- Directory blocks
- Primary allocation
- Secondary allocation
You must either specify all the fields or specify none at all.
System Action:
None.
User Action:
You must specify all fields or none at all. If you specify none, then, for DASD, a default space allocation of one track with no directory blocks is assumed.
Reason:
You must specify either a CMS file name or a ddname (but not both).
System Action:
None.
User Action:
Specify the CMS file name or the ddname, and retry. When specifying a CMS file name, you must specify all three components: file name (FN), file type (FT), and file mode (FM).
Reason:
You must specify either a CMS file name or a ddname (but not both).
System Action:
None.
User Action:
Erase either the CMS file name or the ddname, and retry. To erase the CMS file name, you must erase all three components: file name (FN), file type (FT), and file mode (FM).
Reason:
There are no transmission requests that match the specified selection criteria.
System Action:
None.
User Action:
None.
Reason:
Actions are applicable to inbound requests, outbound requests, or both. The selected action is not applicable to the request direction ( P1 is inbound or outbound).
System Action:
None.
User Action:
Use ?=More Actions to display a list of valid actions for the request.
Reason:
The Q action was used to display a description of the FTS request completion code associated with this request. This code is taken from the first word of the information text. However, the code does not conform to the FTS request completion code format because it is not in the form LOC-xx or REM-xx.
System Action:
None.
User Action:
None.
Reason:
The Q action was used to display a description of the FTS request completion code associated with this request. This code is taken from the first word of the information text but this is blank.
System Action:
None.
User Action:
None.
| Copyright © 2012 CA. All rights reserved. |
|