This page describes messages with message class 1021. These messages have the format:
1021nnnn
where | 1021 | is the message class and |
nnnn | is the message number in the range 0000 - 9999. |
These messages are returned by the Server Mapping Deployment Wizard See Server Mapping Deployment Wizard in the EntireX Workbench documentation.
10210001 | 10210002 | 10210003 | 10210004 | 10210005 | 10210006 | 10210007 | 10210008 | 10210009 | 10210010 | 10210011 | 10210012
10210001 | Entry does not exist |
Explanation |
The server mapping accessed by the deployment service does not exist in the server mapping file. |
Action |
None. |
10210002 | Entry already exists |
Explanation |
If available in your environment, use the overwrite option and retry. |
Action |
Resubmit with 'update' option. |
10210003 | Entry replaced |
Explanation |
An existing server mapping entry was altered. |
Action |
None. |
10210004 | No matching entry |
Explanation |
A |
Action |
None. |
10210005 | Invalid record |
Explanation |
The deployment service received a server mapping file of an unknown format. The request was rejected. |
Action |
Probably version conflict. Check your installation. |
10210006 | Open file error: <reason> |
Explanation |
The Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch) could not open the server-side mapping container. See <reason> and refer to platform documentation for more information. |
Action |
Check your installation. For configuration, see Enabling the Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch). |
10210007 | Write Error: <reason> |
Explanation |
The Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch) could not open the server-side mapping container. See <reason> and refer to platform documentation for more information. |
Action |
Check status and/or authorization of the server-side mapping container. For configuration, see Enabling the Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch). |
10210008 | Read Error: <reason> |
Explanation |
The Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch) could not read from the server-side mapping container. See <reason> and refer to platform documentation for more information. |
Action |
Check status and/or authorization of the server-side mapping container. For configuration, see Enabling the Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch). |
10210009 | Delete Error: <reason> |
Explanation |
The Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch) could not access the server-side mapping container. See <reason> and refer to platform documentation for more information. |
Action |
Check status and/or authorization of the server-side mapping container. For configuration, see Enabling the Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch). |
10210010 | Resource problem: <reason> |
Explanation |
Resource problem with server deployment service, probably lack of storage. See <reason> and refer to platform documentation for more information. |
Action |
Try again later. |
10210011 | DEPLOYMENT service not active |
Explanation |
The RPC server was invoked, but the deployment service itself was not
activated, see RPC server option |
Action |
Ask your system programmer. |
10210012 | Invalid usage of DEPLOYMENT service |
Explanation |
The RPC server received a request for the Deployment Service for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch) for a broker service other than DEPLOYMENT. |
Action |
Use DEPLOYMENT as the broker service name in the deployment environment.
See Step 2b: Define the Connection to the Deployment Service and Deploy under Server Mapping Deployment Wizard in the EntireX Workbench documentation and |