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 deployment wizard of the COBOL Wrapper. See Server Mapping Deployment Wizard.
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 SVM 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 of an unknown format . The request was rejected. |
| Action |
Probably version conflict. Check your installation. |
| 10210006 | Open file error: <reason> |
| Explanation |
The deployment service could not open the SVM file. See <reason> and refer to platform documentation for more information. |
| Action |
Check your installation. For a CICS RPC server, see the file definition
|
| 10210007 | Write Error: <reason> |
| Explanation |
The deployment service could not write to the SVM file. See <reason> and refer to platform documentation for more information. |
| Action |
Check status and/or authorization of the SVM file. For a CICS RPC server,
see the file definition |
| 10210008 | Read Error: <reason> |
| Explanation |
The deployment service could not read from the SVM file. See <reason> and refer to platform documentation for more information. |
| Action |
Check status and/or authorization of the SVM file. For a CICS RPC server,
see the file definition |
| 10210009 | Delete Error: <reason> |
| Explanation |
The deployment service could not read the SVM file. See <reason> and refer to platform documentation for more information. |
| Action |
Check status and/or authorization of the SVM file. For a CICS RPC server,
see the file definition |
| 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 (using the IDL library SAGSVM) for a broker service other than DEPLOYMENT. |
| Action |
For an overview of how to deploy an SVM file see Deployment Service for CICS | Batch | IMS | Micro Focus | BS2000/OSD) | z/VSE (separate 7.2.3 documentation). Use DEPLOYMENT as the broker service name in the deployment environment. See Step 2b: Define the Connection to the Deployment Service and Deploy. |
