A list of the values that can be set in the ERROR field
of an ACB follow (ACBERFLG is the actual field name). See
z/OS Communications Server: SNA Programming for a description of the OPEN macro.
- 0 (X'00')
- OPEN successfully opened this ACB.
- 4 (X'04')
- The ACB has been opened.
- 20 (X'14')
- OPEN cannot be processed because of a temporary shortage of storage.
- 36 (X'24')
- The OPEN ACB failed for one of the following reasons:
- The password specified by the ACB did not match the corresponding
password in the APPL entry.
- The ACB did not specify a password and the APPL contains one.
- The
security management product determined that the user is not authorized
to open the ACB.
- 70 (X'46')
- OPEN was issued in an exit routine.
- 80 (X'50')
- VTAM® has not been included
as part of the operating system. The fault lies in the system definition
procedures.
- 82 (X'52')
- VTAM is included as part
of the operating system, but the VTAM operator
issued a HALT command, and VTAM has
shut down. You cannot attempt to establish a session or communicate
with any LUs.
- 84 (X'54')
- Either the address supplied in the ACB's APPLID field lies beyond
the addressable range of your application program, or no entry is
found in the VTAM configuration
tables that matches the name indicated by the ACB's APPLID field (or
supplied by the operating system). If the OPEN macro is specified
correctly, your system programmer might have:
- Failed to include your application program's symbolic name during VTAM definition
- Improperly handled the symbolic name
See the description of the APPLID operand in the ACB macro.
- 86 (X'56')
- A match for your application program's symbolic name is found,
but it is for an entry other than an APPL. If you specified this name
in the ACB's APPLID field, verify that you have the correct name and
handled this name properly (see the APPLID operand of the ACB macro).
If the symbolic name is supplied by the operating system, the supplied
name is suspect.
- 88 (X'58')
- Another ACB, already opened by VTAM,
indicates the same application program symbolic name that this ACB
does. The system programmer might have assigned the same symbolic
name to two application programs. This is valid only if the programs
are not open concurrently. Possibly the system operator initiated
your program at the wrong time.
For multinode persistent session
support, an MNPS takeover OPEN was rejected by the owning VTAM node.
- 90 (X'5A')
- No entry is found in the VTAM configuration
tables that matches the name indicated by the ACB APPLID field (or
supplied by the operating system). This error might have occurred
for one of the following reasons:
- The VTAM operator deactivated
the APPL entry
- The APPL entry was never created
- VTAM is trying to recover
for persistent sessions and the application is not in pending recovery
state
- 92 (X'5C')
- VTAM is included as part
of the operating system but inactive.
- 94 (X'5E')
- The address supplied in the ACB APPLID field lies beyond the addressable
range of your application program.
- 95 (X'5F')
- The VTAM transient being
used by the application for an OPEN ACB does not match the level of VTAM. The correct level of VTAM is not in the LIBDEF search
chain for the application.
- 96 (X'60')
- An apparent system error occurred. Either there is a defect in VTAM logic, or there is an error
in your use of OPEN or CLOSE that VTAM did
not properly detect. Save all applicable program listings and storage
dumps, and consult your IBM® programming
services representative.
- 98 (X'62')
- The APPLID length byte is incorrectly specified.
- 100 (X'64')
- The address supplied in the ACB's PASSWD field lies beyond the
addressable range of your application program.
- 102 (X'66')
- The PASSWD length byte is incorrectly specified.
- 104 (X'68')
- The APPLID field in the ACB identifies an application program
that is defined with AUTH=PPO in its APPL definition statement. Another
program with the same authorization is active. Only one program defined
with AUTH=PPO can be active at a time.
- 106 (X'6A')
- The address supplied in the ACB's vector list field lies beyond
the addressable range of your application program.
- 108 (X'6C')
- The ACB vector list length byte is incorrectly specified.
- 112 (X'70')
- You attempted to open an ACB that is in the process of being closed.
This can occur when a VTAM application
program job step or subtask is canceled or terminates abnormally.
The process of closing the ACB can continue after the job step or
subtask has actually terminated. Subsequently, if the job step is
restarted or the subtask is reattached before the ACB closing process
has been completed, an OPEN macro that is then issued for that ACB
fails.
- 114 (X'72')
- This
code occurs from an open ACB failure for the VTAM CP when VERIFYCP is coded as a start option
or for an OPEN ACB failure for an LU 6.2 application with VERIFY=OPTIONAL
or VERIFY=REQUIRED for one of the following reasons:
- The security management product is not installed.
- The security management product is not active.
- The security management product resource class APPCLU is not active.
- The application represented by the ACB is not in the security
management product Started Procedures Table.
- 116 (X'74')
- VTAM rejected the takeover by an
alternate application because the original application did not enable
persistence, although it is capable of persistence.
- 118 (X'76')
- OPEN failed for one of the following reasons:
- The specified application is in a recovery pending state and PERSIST=YES
is not specified on the ACB that is being opened
- The application is in pending terminate state and an active CDRSC
with the same name has been found in the sysplex
- 120 (X'78')
- ACB
or APPL statement option mismatch between original application and
opening takeover or recovery application. One or more of the following
situations can apply:
- APPC mismatch—both application APPL statements must specify
either APPC=YES or APPC=NO; they cannot differ.
- ENCR or MAC mismatch—the recovering application APPL statement
must specify a security level equal to or higher than the setting
in effect for the original application.
- ENCRTYPE mismatch—the recovering application APPL statement
must specify a minimum encryption level equal to or higher than the
setting in effect for the original application.
- FDX mismatch—both applications must be specified as FDX=YES
or FDX=NO; they cannot differ
- GNAME capability mismatch—the original application was supporting
a generic name but the VTAM node
of the recovering application is not connected to a generic resource
structure or its structure name differs from the original structure
name.
- ISTVAC81 vector mismatch—the application capabilities vector
provided by the recovering application does not match that of the
original application.
- LIMQSINT mismatch—both application APPL statements must
agree in their specification of a LIMQSINT parameter; either both
must specify a value or neither must specify a value. However, the
actual timer values specified do not need to be identical.
- MACRF mismatch—both values must be either LOGON or NLOGON;
they cannot differ.
- NQNAMES mismatch—both applications must be specified as
NQNAMES=YES or NQNAMES=NO; they cannot differ.
- PERSIST mismatch—both applications must be specified as
PERSIST=YES or PERSIST=NO; they cannot differ.
- SECLVL mismatch—both application APPL statements must specify
the same SECLVL setting values; they cannot differ.
- VERIFY mismatch—both application APPL statements must specify
the same VERIFY setting values; they cannot differ.
- 122 (X'7A')
- The OPEN ACB issued by a monitor application was rejected because
a monitor application was already active on this VTAM.
- 124 (X'7C')
- The OPEN ACB that would have resulted in SNPS takeover processing
was rejected because the active application does not support SNPS
takeover requests.
- 188 (X'BC')
- The ACB is in the process of being opened or closed by another
request.
- 244 (X'F4')
- The
application program is not authorized for SRBEXIT=YES. A request to
open an ACB whose corresponding APPL definition statement specifies
SRBEXIT=YES is rejected unless the application program is APF authorized,
or using key 0–7, or in supervisor state.
- 246 (X'F6')
- NIB storage address not valid. A CNM authorized application program
either failed to supply an NIB pointer in the NIB field of the ACB,
or the NIB address supplied lies beyond the addressable range of the
application program.
- 250 (X'FA')
- NIB options not valid. Either an application program without CNM
authorization (specified in its associated VTAM resource definition) supplied an NIB pointer
in its ACB; or, if CNM authorized, the application program failed
to supply valid NIB options on the NIB macro.
- 254 (X'FE')
- Duplicate unsolicited RU routing requested. The CNM routing table
indicated that this application program was to receive the same unsolicited
formatted requests that were already being routed to another active
CNM authorized application program. Only one application program can
be actively receiving a particular type of RU (for example, RECFMS)
at a time.