Status Codes
After completion of the @BIND SUBSCH function, the ERRSTAT field in the IDMS communications block indicates the outcome of the operation. The following is a list of the acceptable status codes for this function and their corresponding meaning:
The request has been serviced successfully.
The @BIND SUBSCH statement cannot be recognized. This code usually indicates that the IDMS communications block (SUBSCHEMA-CTRL) is not aligned on a fullword boundary.
The subschema invoked does not match the subschema object tables.
The run unit is not bound to the DBMS. This code indicates that the central version is not active or is not accepting new run units, or that the run unit's connection to the central version is broken due to timeout or other factors, as noted on the CV log.
The journal file will not open (local mode only); under OS, the most probable cause is that a DD statement for the journal file is missing in the JCL.
The available memory is insufficient to dynamically load a subschema or database procedure.
The central version is not accepting new run units.
The subschema was not found in the dictionary load area or in the load library.
The run unit has been bound previously.
The node specified in the NODENAME clause either is not active or has been disabled from the communications network.
The database specified in the CA IDMS network clause is not known to CA IDMS/DB.
The named subschema is not allowed under the database specified in the DBNAME clause.
The available memory is insufficient to allocate native VSAM work areas.
|
Copyright © 2014 CA.
All rights reserved.
|
|