DOCS

Release 7.2
Messages and Codes

Copyright © 2001 by Software Pursuits, Inc.
All Rights Reserved.

Except as noted below, no part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise without the prior written permission of Software Pursuits, Inc.

Table of Contents


Introduction

TOP
This publication applies to the Software Pursuits, Inc. Display Operator Console System (DOCS) program product.

Message Format

All messages, unless otherwise specified, are in the format:

DOCnnn[t] message...

Where:

DOC
Indicates that the message is being issued by the DOCS product.
nnn
The assigned number for a given message.
t
Indicates the type of message being issued.
A
An action message. Some type of action is required for processing to continue. The actual action(s) required will depend on the program processing and the activity being performed.
C
A cancellation message. A severe error has occurred that caused processing to be canceled.
D
A decision is required. Some type of decision is required that will require a response to the message.
I
An informational message. Action is not generally required.
E
A severe error message. Some type of action is required to complete the processing.
W
A warning message. A moderately severe error has occurred that may or may not require action.
message
The message text.

0xx Prefix

TOP

DOC001 DOCS Already executing

DOCSMAIN is operational. A future release of DOCS will permit re-submission of configuration definitions after DOCS is running.
DOC002 GETVIS failure for phase phasename Rtrn Code = rc
The DOCS initiator issued a GETVIS to obtain space in the SVA for the specified phase or for the user profile table and the indicated return code was returned by the supervisor.

If the phase name indicates SVA GET, the system GETVIS area is not large enough to accommodate the DOCS master screen phases and/or $DOCS phases which were not loaded to the SVA.

If the phase name indicates SUPPRESS, the partition GETVIS area is not large enough to accommodate the data suppression tables in the initiating region/partition.

If PROFILES is shown, the system GETVIS area must be made larger to accommodate the user profile table entries and/or the data suppression tables. Refer to 'Storage Requirements' in Appendix A for additional information.

Otherwise, if the phase name shown begins with $, the GETVIS failure can be prevented by loading all of the DOCS phases which begin with $DOCS and followed by three alpha characters, to the SDL.

DOC003 xxxxxx macro failure, return code = rc
The named macro failed with the indicated return code (decimal value). DOCS discontinues any attempt to activate. Contact SPI Technical Support.
DOC004 CDLOAD failure for phasename, Return Code = rc
The DOCS initiator issued a CDLOAD macro (SVC 65) to obtain space in the partition GETVIS area and the detailed return code was returned by the supervisor. The CDLOAD macro is used to load DOCS phases into region/partition GETVIS during initialization. You may either:
DOC005 Unable to locate SYSOCDEV reference in Supvr
DOCS uses this label as a hook point in the supervisor. DOCS was unable to locate the proper hook point.
DOC006 Insufficient room to load DOCSnn
DOCS was unable to load the indicated phase in the virtual BG partition to load the indicated phase. You may either:
DOC007 BG REAL too small - nnnK additional required.
The Fx area where DOCSMAIN is to be loaded is obtained by removing storage from the BG real partition. The size of BG real should be allocated to a larger amount than that required by DOCSMAIN to allow flexibility when DOCS is initialized. After DOCS is operational, and storage remaining in BG real may be reallocated elsewhere.
DOC008 EDOS/VS requires V=V for DOCS
DOCS will only operate with a supervisor which supports virtual partitions. DOCS requires the SVA and GETVIS area.
DOC009 The following phase cannot be located: phasename
The named phase was not found when trying to load its directory entry. Be sure that all of the DOCS phases have been cataloged to the proper core image library.
DOC010 Unable to issue GETREAL or PFIX for DOCS, Rtrn Code = rc
The DOCS initiator uses either the GETREAL of PFIX facility for systems running in S/370 mode or ECPS mode respectively. The indicated return code was returned by the supervisor when the DOCS transient $$BDOCSL attempted to use the appropriate function.

This error will generally result from insufficient real or virtual storage being allocated to the BG partition. Increase the partition allocation(s) beyond that required by the DOCS initiator since any storage not used by DOCSMAIN in the Fx area may be recovered by the appropriate allocation after DOCS is active.

DOC011 Allocated IUCV external buffer too small. nnn bytes required. IUCV ignored
The anticipated IUCV buffer size exceeds the allocated area in DOCSMAIN. Please contact SPI Technical Support.
DOC012 FBA extent too small
An FBA extent was specified for the DOCSHC hardcopy file which would not accommodate at least 2 logical blocks, the minimum size permitted. The extent must be made larger.
DOC013 Unable to locate R1 LTA save area ptr
$$BDOCSL cannot locate the R1 save area pointer in the LTA save area. This is an internal program error when DOCS is running under MVT/VSE in ECPS mode. Please contact SPI Technical Support.
DOC014 Synonym synonym out of range
A user specified synonym is beyond the limits of the control phase. The synonym number (#nn) is not replaced.
DOC015 DOCS has expired. Please contact Software Pursuits
The DOCS product has expired. Please contact SPI Technical Support.
DOC016 Cannot use device=cuu, unit assigned as SYSLOG
DOCS cannot use the indicated device because it is assigned as SYSLOG and the VSE/ESA Version 2 system. DOCS' activation will continue, but DOCS will not use the indicated device.
DOC017 Control phase phasename invalid or phase not found
The phase name specified on the CONTROL= definition either:

Verify that the correct phase is specified and properly cataloged to the core image library.

DOC018 No control phase specified for synonym synonym
A synonym value was specified for a definition but a CONTROL= definition has not been specified to identify the origin of the synonyms.
DOC019 I/O Error X'cuu' Status X'ss' Sense X'nn' Requested record addr = X'addr'
This message is normal for terminals that are not turned on or not dialed to the virtual machine when DOCS is being initiated. The DOCS initiator issues an SVC 0 (EXCP) to each device assigned to it to determine the status and descriptive characteristics of the device. The error message reflects a unit check which was received from the SVC 0. The status and sense bytes detail the cause of the error.

If a device is not ready when the DOCS initialization references it, an assumption is made about the device characteristics unless the MODEL= definition has been submitted to reserve sufficient storage for other than the default device type. The following assumptions are made:

  1. The device is assumed to be a display or printer without extended color and highlighting facilities.
  2. If the device is a display unit and the channel and unit address of the device is not greater than X'01F', the device is assumed to be a 3278-2A (20 lines). If the device is a display unit and the channel and unit address is greater than X'01F', the device is assumed to be a 24 line display unit.

If a device is not operational when the DOCS initialization references it, the device will not be used by DOCS even if the initiator is successful in bringing up DOCSMAIN. A not operational device is indicated by a status byte of X'00' and a sense byte usually of X'FE'.

This message is also used by the DUMP function of DOCSUTIL to indicate an I/O error on the input dump tape. The requested dump record address is also shown along with the routine address in DOCSUTIL.

DOC020 No usable 3277s. See error code above
The DOCS initiator was unable to reference any usable display units. The error indications for any devices which were assigned for DOCS use are detailed by error code 019.
DOC021 DOCS must be executed in virtual mode
The DOCS initialization must take place in a virtual partition. DOCS should be initialized immediately after IPL. Systems, which support automatic initialization, should include the DOCS initialization assignments and configuration definitions in the procedure used to IPL the system.
DOC022 DOCS / VMCF interface enabled
The DOCS / VMCF interface has been directly enabled by the DOCS initiator. The default $VMCF SVA phase will not be used.
DOC023 BG Virtual Partition nnK too small to load Fx area
The initiating partition is too small by the number of K bytes specified. This generally is caused by a SIZE= operand on the EXEC statement being too small. Increase the value for the SIZE= operand or the size of the virtual partition.
DOC024 DOCS format control record missing. Hard copy not available
This error code is used by the LIST function of DOCSUTIL. The open for the hardcopy file was successful; however, the first logical record in the file does not contain the constant used by an earlier version of DOCS or a user program had inadvertently overlaid the beginning of the DOCS hardcopy file.
DOC025 SYS000 must be assigned to a CKD or FBA DASD device
Either the DOCS initiator or DOCSUTIL found SYS000 to be assigned to an invalid device type. If it is desired to initialize DOCS without a hardcopy file, SYS000 should be left unassigned or assigned to IGN.
DOC026 Insufficient room for temporary device ctrl block
The DOCS initialization phase builds a temporary device control block for each device which is assigned to it. These temporary device control blocks are constructed in the virtual BG partition. The virtual partition is not large enough to accommodate all of the device control blocks associated with the devices that DOCS is to use. Calculate the amount of storage required from the tables shown in the DOCS installation instructions.
DOC027 Unknown display buffer size of nnnn for X'cuu'
The DOCS initiator determines the buffer size of each display unit that is assigned to it via a read buffer command. The size calculated for the device address shown is not a recognizable buffer size. The following defaults are assumed:

This may also be a hardware error.

DOC028 DOCSMAIN will require nnK of real storage at address
This is an informational message to inform the operator what the real storage requirements are for DOCSMAIN and the address where DOCSMAIN will reside.
DOC029 DOCS v.m.p (addr) COPYRIGHT 1975-1995 by SPI, Inc.
This is an informational message which is always the first SYSLOG data line displayed on all display consoles and trickle printers, which do not exclude the BG partition, following the messages which were written to the traditional SYSLOG device. v.m.p is the version, modification and PTF level of DOCS. addr is the address of the area where DOCSMAIN is loaded.
DOC030 Hard copy not assigned or in error
The hardcopy file (SYS000 during initialization) was either unassigned or an error occurred while trying to open the file. DOCS is initialized without any hardcopy file. Paging and End of Job logging are suppressed.
DOC031 Hard copy file being formatted
The DOCS initialization routine has determined that the hardcopy file must be formatted. The possible reasons for the hardcopy file being formatted are:
DOC032 Hard copy file open failure
The steps detailed in error code 031 have been executed and then an output open of the DOCSHC file is attempted. If the output open fails, this error message is written to SYSLOG and initialization continues without any hardcopy file. This is generally due to an incorrect // DLBL or // EXTENT statement.
DOC033 Hard copy extent in error
The // EXTENT statement defining the limits for the DOCSHC file was found to be invalid. The hardcopy file extent must begin on a cylinder boundary for a CKD device.
DOC034 Formatting error at CC cyl HH head RR record
An I/O error occurred while formatting a CKD extent. This is a hardware error. Select a different area on the same volume or select another volume for the hardcopy device.
DOC035 Formatting error in block num block
An I/O error occurred while formatting an FBA extent. This is a hardware error. Select a different area on the same volume or select another volume for the hardcopy device.
DOC036 Hard copy file warm started
This is an informational message that informs the operator that the hardcopy file has been warm started. This message does not appear if the hardcopy file exists but has been cleared with DOCSUTIL.
DOC037 nnn (nnn%) Records listed from the DOCS hard copy file
This is an informational message issued by the LIST function of DOSUTIL when the hardcopy file is printed. This message is always written to SYSLOG. When the LIST function is run as a batch program rather than as a subroutine in a user program, the message is also printed on SYSLST following the listing of the file.

nn.n% indicates the percentage of the hardcopy file represented by the number of records listed.

DOC038 Hard copy file has been cleared
This is an informational message output to SYSLOG by DOCSUTIL to inform the operator that the hardcopy file has been listed and cleared.
DOC039 Hard copy file partially cleared by DOCSUTIL. Should file be overwritten?
The hardcopy file has been partially cleared by either the LIST function of DOCSUTIL or a user program using the LIST function as a subroutine to access the hardcopy file. The indication that the file is partially cleared is the presence of 'LIST' in bytes 12-15 of the first logical record of the hardcopy file. In order for DOCS to be initialized with hardcopy support, DOCSUTIL or the user program must be run to normal completion to have the control record reset.

The operator is given the option of replying 'YES' to cause the hardcopy file to be reformatted or 'NO' in which case DOCS will be initialized without a hardcopy file.

DOC040 Enter cmd OR (id |)data_nn
DOCS has been executed from SYSLOG and the initiator is now prompting for configuration definitions; or, DOCS has been executed from SYSRDR (or within a cataloged procedure) and this message is written to prompt for an operator reply to the message immediately preceding this message.

Configuration definitions entered via SYSLOG are in the same format as if they were entered on statements via SYSIPT.

DOC041 Entry accepted
The previous configuration definition was verified as correct and has been accepted.
DOC042 xxxxxx - Entry rejected
The previous configuration definition was rejected. Refer to the DOCS customizing definitions for a full description of format and content of the possible configuration definitions.
DOC043 color - Unknown color name for 3279
The detailed color name is not valid. Any number of characters of a color name may be specified, from 1 to the number of characters in the full name. Valid color names are: Blue, Red, Pink, Green, Turquoise, Yellow and White.
DOC044 Invalid SYSxxx - Flush to next dev specification
The specified programmer logical unit number does not correspond to a valid device assignment. All configuration definitions following this device specification are flushed until the next device specification.
DOC045 SYSxxx was not available during DOCS initialization
The specified device could not be successfully referenced by the DOCS initialization I/O routine; therefore, all configuration definitions for this device are ignored and flushed.
DOC046 FLWG should not begin in col 1. Applies only to [SYSnnn | profilename]
The detailed configuration definition began in column 1 of the input statement yet it was preceded by a device specification statement (SYSnnn) or PROFILE statement. The definition is accepted but it is applied to only the device detailed in the previous device specification of the user profile detailed in the previous PROFILE statement.
DOC047 FLWG should begin in col1. Will be applied to all dev
The detailed configuration definition should have begun in column 1 of the input statement if it was intended to apply to all devices. If it was intended to apply to a particular device, the device specification definition is omitted.
DOC048 Partition id of id invalid for definition. Ignored
The partition SYSLOG Id indicated is not acceptable as a definition argument. Only Rx, BG, Fx and CP may be specified. In the event that a program alters its' SYSLOG ID in the PIB table, the original region or partition ID must be specified.
DOC049 SYS001 may not be excluded
The display console assigned as SYS001 may not be excluded. This is to prevent a partition from being excluded completely, effectively eliminating SYSLOG for that region/partition.
DOC050 Invalid option for definition parameter. Ignored
An invalid DOCS definition has been specified. Refer to the DOCS documentation for a complete description of valid definitions.
DOC051 Hard copy vers/mod incorrect. Should file be overwritten?
The DOCS hardcopy file was formatted at an earlier level than the current level of DOCS and the definition of the file has changed.

The hardcopy file should have been printed using the prior level of DOCSUTIL, or with a user program that included the LIST subroutine if there is data on the hardcopy file which is to be retained.

The operator may reply 'YES' to cause the hardcopy file to be reformatted with the correct version & modification level or 'NO' to initialize DOCS without using the hardcopy file.

DOC052 Hard copy blocking factor incorrect. Should file be overwritten?
Refer to the description of the DOCS051 message.
DOC053 Hard copy file nnn% FULL
This message details the current capacity of the hardcopy file.
DOC054 Unable to locate EXTRTN. IUCV support disabled
The DOCS initiator was unable to locate the instructions at the label EXTRTN. IUCV cannot be enabled. Contact SPI Technical Support.
DOC055 Unable to locate LOGCCW. IUCV support disabled
The DOCS initiator was unable to locate the code at the label LOGCCW. IUCV cannot be enabled. Contact SPI Technical Support.
DOC056 Unable to locate emergency message writer code
The DOCS initiator must locate a specific instruction in the emergency message writer code in DOS/VSE Release 37 (AF3). DOCS was unable to locate the proper hook point. DOCS will terminate the operation. Please contact SPI Technical Support.
DOC057 Master screen phase name of phasename for X'cuu' unknown
The DOCS initiator calculated a master screen phase name as specified in this error message. DOCS was unable to locate the specified phase. This is generally caused by the phase being cataloged to the wrong library.
DOC058 DOCS should be initialized before VSE/POWER
VSE/POWER was initialized prior to DOCS. It is recommended that DOCS be initialized within the ASI procedure prior to any batch job execution.
DOC059 Invalid loan return arg - arg
A loan return definition was submitted to the DOCS initiator which does not conform to the specifications for this definition. Refer to the DOCS documentation for specific information on device related definitions.
DOC060 Unable to locate APMGMDAT and/or ASVPFREE, SYSxxx not loanable
The DOCS initiator was unable to locate one of the above referenced address constants. Without these address constants, the DEVICE ON LOAN facility will not operate properly. Please contact SPI Technical Support.
DOC061 Suppression table work area size of X'nnnn' exceeded for SYSnnn
The data suppression argument table submitted for the specified device exceeds the allocated work area size shown. Please contact SPI Technical Support.
DOC062 DOCSnn (v.m) INITIALIZATION ROUTINE LOADED AT X'address'
This message identifies the DOCS initialization phase name along with the location where it is loaded and version and modification level.

Once this message appears, a MSG BG command may be entered to prohibit DOCS from enabling. This is used in the event that the user wishes initialize DOCS for test purposes. To get the DOCS PTF level, see message DOCS029 or use the $B or DOCSAPAR commands.

DOC063 // JOB stmt should not precede DOCS initialization
DOCS should be executed prior to the first JOB statement being read by job control to eliminate both the time and space required by the IJSYSCN file.
DOC064 DOCS requires a virtual machine to have either class C or E privilege
The VM directory for the virtual machine that DOCS is running under must specify either class C or class E commands.
DOC065 VSIUCV open failure. Return code = rc
The DOCS initiator attempted to issue an OPEN and received the above return code.
DOC066 VSIUCV connect to id failed. Return code = rc
The DOCS initiator attempted to connect to the ID shown above and received the return code specified.
DOC067 IUCV query unsupported. IUCV not available
The DOCS initiator issued an IUCV Query command that was rejected.
DOC068 nnn IUCV paths available. IUCV will be enabled
The numbers of paths shown are available for IUCV use by this virtual machine. The number of paths reflects the MAXCONN value specified in the OPTION control statement in the virtual machine directory. The default MAXCONN value is 4.
DOC069 SYSnnn is the 2nd assignment to cuu
More than one logical unit (SYSnnn) is assigned to the address shown above. All but the first assignment are ignored.
DOC070 Unable to locate HC File hook point.
The DOCS initiator was unable to locate a specific instruction sequence in the module $IJBSHCF on Version 2 of VSE/ESA. DOCS discontinues any attempt to activate. Please contact SPI Technical Support.
DOC071 MODEL=mm is not a valid display model type
The default model specification (mm) is not a valid display unit type. Refer to the DOCS customization options for detailed information.
DOC072 PWRD= Specification invalid: password
The value specified as a password does not conform to the parameter definition. Refer to the DOCS documentation for detailed information on the use of the PWRD= operand.
DOC073 Insufficient storage for temporary user profile entry
The DOCS initialization phase builds a temporary user profile control block for each PROFILE definition submitted plus one temporary user block for each console. These temporary user profile blocks are constructed in the virtual BG partition. The virtual partition is not large enough to accommodate all of the user profile control blocks required. Refer to the DOCS documentation for detailed information on calculating storage estimates.
DOC074 Profile contains invalid USER= Specification, ignored
The operator identification submitted with the profile definition does not conform to the specifications for the USER= value. The user profile entry is ignored.
DOC075 Hard copy file owned by CPU cpuid. Should file be overwritten?
An attempt was made to open a DOCS hardcopy file that was created under a different CPU identification (last 5 characters only). This is generally due to an incorrect DLBL and/or EXTENT statement during initialization.

The operator may reply 'YES' to cause the hardcopy file to be reformatted with the correct CPU identification or 'NO' to cause DOCS to initialize without using a hardcopy file.

A reply of 'OK' will allow the DOCS initiator to continue as if the CPU identification was correct.

DOC076 USER= Specification invalid: specification
The value specified as an Operator Id does not conform to the parameter definition. Refer to the DOCS documentation for details on the use of the USER= statement.
DOC077 No user profile specified for SYSnnn - Oper Id = id
LOGON=id was indicated in the device specification for the unit shown in the message; however, a user profile was not supplied with a matching operator identification. The device will not assume the profile specifications; however, the device will be available if it had been logged on.
DOC078 Device specification may not follow profile entry
A device specification statement, SYSnnn, followed a profile entry, PROFILE USER=, in the configuration definitions. Correct the configuration definition and reinitialize DOCS.
DOC079 Unable to locate end of SVC 0 routine
The DOCS initiator scans for the end of the SVC 00 routine in the supervisor. This is an internal program error in the DOCS initiator. Contact SPI Technical support.
DOC080 SYS001 must not be assigned to a type type printer
SYS001 must be assigned to a display unit. The DOCS initiator found SYS001 to be assigned to either a 3215 or 328X printer. Correct the assignment and reinitialize DOCS.
DOC081 LOGON= Specification invalid: operid
The value specified as automatic logon operator identification does not conform to the parameter definition. Refer to the DOCS documentation for details on the use of the LOGON= definition.
DOC082 OK to clear hard copy file from CPU cpuid?
The LIST function has been executed with the clear option for a hardcopy file that belongs to another CPU. The user may reply either 'YES' to clear the hardcopy file or 'NO' to list the hardcopy file without it being cleared.

If 'YES' is entered to cause the hardcopy file to be cleared, it is the users responsibility to assure that the system to which the hardcopy file belongs is not active. If this is not the case, all SYSLOG data on that system will be lost.

DOC083 DOCSUTIL clearing/formatting HC file in another partition
DOCSUTIL was executed to list and clear the hardcopy file; however, it was already running in another partition. The second execution of DOCSUTIL will continue without the clear request.
DOC084 LOGOFF= Specification invalid: specification
The value specified as a logoff screen image does not conform to the parameter definition. Refer to the DOCS documentation for details on the use of the LOGOFF= statement.
DOC085 Logoff SCREEN phase phasename missing or invalid
The phase name shown was either not found or does not conform to the specifications for a user logoff screen phase. The DOCS logoff logo will be used in place of the user-defined phase when the LOGOFF command is issued.
DOC086 DOCS initialization bypassed because of OC interrupt
An Attention Routine MSG command was issued while the initialization phase was running. This external interrupt causes the DOCS initiator to perform all of its normal processing except that the resident portion of DOCS is not loaded and enabled. This function is provided for test purposes only.
DOC087 Unable to locate enable in CCWTRANS
The DOCS initiator could not locate the code in the supervisor used to enable interrupts in CCWTRANS. Please contact SPI Technical Support.
DOC088 Unable to locate TSCH or STSCH in supvr
The TSCH or STSCH instruction in the I/O interrupt handler of a MODE=ESA supervisor could not be located. Please contact SPI Technical Support.
DOC089 DOCS not operational
A DOCS batch utility was executed when DOCS was not active. Be sure DOCS is active prior to using the DOCS batch facility.
DOC090 Partition size exceeded, auto-reply canceled
DOCSUTIL did not have enough storage in the partition where it was running to build its command table. This is probably caused by excessive data being read by DOCSUTIL.
DOC091 [GET | FREE]VIS error, Return Code = rc
DOCSUTIL issued either a FREEVIS to release previously used system GETVIS storage or a GETVIS to acquire system GETVIS storage and received the error detailed in the message.
DOC092 Unable to locate code at 'SVCINDEX'
The DOCS Initiator could not locate the code in the Supervisor to which it will pass SVC interrupts. Please contact SPI Technical Support.
DOC093 nnn Auto-reply response lines loaded for id
This message shows the number of auto-replies that have been loaded to GETVIS for the indicated region/partition.
DOC094 v.m V.M DOES NOT MATCH DOCS INIT V.M
The version/modification level of the DOCS phase shown is at a different level than the DOCS initiator.

This will generally be caused by a prior level of the phase residing in the system core image library. Delete the old phase from library and ensure that all phases are of the same level prior to any activation.

DOC095 IUCV Query Condition Code or Pgm Check error. IUCV not available.
The DOCS initiator issued an IUCV Query that resulted in either a non-zero condition code or a program check. Neither of these situations should occur. Please contact SPI Technical Support.
DOC096 Unable to locate hard wait code
The DOCS initiator could not locate the code used in the supervisor to force a hard wait. As a result, the DOCS hard wait processing cannot occur.
DOC097 Minutes invalid for auto $- Command
The number of minutes specified for an automatic logoff or CP RESET is invalid and ignored.
DOC098 CPRESET addr invalid - cuu
The value specified in the CPRESET definition must be a valid channel and unit address. The CPRESET definition is ignored.
DOC099 Key word auto-reply invalid, pre-replies canceled
A keyword auto-reply must have:

If a keyword displacement is specified, it must be enclosed within parenthesis and contain a numeric value between 0-63.

1xx Prefix

TOP

DOC100 Invalid Id

The preceding entry specified a SYSLOG Id for a partition or pseudo partition that does not currently have an outstanding read. A data keyed in the data portion of the entry line is rewritten in high intensity in the event that a keying error was made in the ID field. If the entry line is to be disregarded, the ERASE INPUT key should be used to clear the entry.
DOC101 Invalid partition selection X'nn'
The SYSLOG Id in the previous entry was for a partition or pseudo partition (CP) that is input restricted at this display console.
DOC102 X'nn' is an unknown aid
The detailed AID (attention identification) is either not a valid 3270 AID or, if the user has altered the AID translate table in DOCSMAIN, the specified AID has been omitted.
DOC103 DOCS program error at addr address - Cancel Codes = cc
This on-line error message is used when an internal error occurs within DOCS, which is not expected. Please take a stand alone dump and contact SPI Technical Support.

The DUMP function will print the contents of this message when it finds that DOCS has abended.

DOC104 Intv ... ... ...
An I/O error has been detected by DOCSMAIN requiring operator intervention. The data detailing the error condition may be in one of the following formats:

This missing interrupt handler facility, unrelated to the VSE missing interrupt handler facility, prevents DOCS from becoming WAIT bound when an I/O interrupt from a DOCS device is lost.

A device will only be included in the DOC104 message when it physically goes from ready to not ready and will not be shown again until it again goes from ready to not ready.

The status of all consoles is available through the use of the ?C inquiry command.

DOC105 Enter ID & data
This message prompts the typewriter operator to key a SYSLOG Id and data after the REQUEST key has been depressed. No space is included between the ID and the data. Single character SPOOLer commands may be entered without including the SYSLOG ID.
DOC106 Hard copy file nn% full
This message details the current capacity of the hardcopy file.
DOC107 Hard copy suspended
An I/O error occurred while trying to read the DOCS hardcopy file. The function, which was trying to read the file, is suspended until the error condition is resolved. The function will then continue.
DOC108 Hard copy canceled
A permanent error occurred while writing a hardcopy file block. The hardcopy file will be restarted, if possible, after standard error recovery has completed. During the time that the hardcopy file is unusable, all data lines written to SYSLOG will be appended with DOC108. This is used to inform the operator that the line has not been written to the hardcopy file.

Also, each line appended with this message number will be made permanent high intensity on standard display consoles and will be changed to red on extended 3279 display consoles. These permanent high intensity lines will be allowed to roll off on standard display consoles.

DOC109 Data entered for restricted Id
The operator attempted to enter data for a SYSLOG Id which is restricted from the display console or the typewriter that received the error message. This condition can occur from either making an entry with the explicit SYSLOG ID or from attempting to enter data which would assume a restricted SYSLOG ID from either a canned command or from the default SYSLOG ID for the device.
DOC110 CP Error code rc
A command passed to CP returned the indicated error. Refer to the proper VM documentation for additional information.
DOC111 No routine linkage for id
An OC (Operator Communication) interrupt was issued for a partition that did not have an OC STXIT linkage established.
DOC112 PF key nn update by id on cuu
This message is appended to all on-line program function key update lines in the hardcopy file. It provides an audit trail showing the contents of the canned command for the specified PF key along with the address of the device for which the canned command was entered.
DOC113 OC routine currently active
The OC (Operator Communication) routine, which the operator attempted to activate, was already in use. When the SYSLOG Id is AR, an attention command for logical attention was entered and either the Attention routine was busy or the Logical Transient Area (LTA) used by AR was in use. The entered AR command is not processed.
DOC114 Parameters restricted
The operator entered a [//] ID USER=... data security command or some other type of secured data (i.e., a password). This message replaces the contents of the entered data on all display consoles and in the DOCS hardcopy file.
DOC115 From id, data
When a device is borrowed by a problem program and then returned to DOCS, any unsolicited write to the display unit from the borrowing problem program will be written to the device as a DOCS system operator message. The SYSLOG region/partition ID and the data written to the device are shown.
DOC116 P: data A: data
The Data Compare Facility was activated to asynchronously monitor storage or general purpose register alteration and a true condition occurred. The PSW, address, logical operator (if any) and the value of the monitored area are shown. More than one true condition may have occurred. This message reflects the most recent occurrence.
DOC117 P: data A: data
The Data Compare Facility was activated to monitor storage or general-purpose register alteration and a true condition occurred causing the system to be placed in a re-startable hard wait.

The current PSW has an address of DDDDDD. The address of the instruction, which caused the true condition, will be found in the second half of the Program Old PSW (X'2C). and the contents of the general registers are the same as when the true condition occurred. Performing a PSW RESTART may restart the system.

Should it be necessary to deactivate the hardware program event recording facility, control register 9 may be set to zero prior to the PSW RESTART.

DOC118 personal comment
A personal comment entry is echoed in the system to operator message area with this message number prefix to indicate that the message has been processed.
DOC119 Enter password
A function has been entered that requires a password. The password must be keyed in the data area of the entry line of the display console and entered via the ENTER key. The password will not appear on the display console as it is keyed.

The password request may be canceled by depressing either the PA1 or the CLEAR Key.

DOC120 id jobname referenced X'cuu' which is not loanable
The indicated job executing in the specified partition attempted to issue I/O for a DOCS console which was defined as being not loanable. All references to the DOCS device are processed as if the partition assignment to the device was 'IGN'.

This error message is broadcast to all display consoles only once per job.

DOC121 Previous entry
The operator depressed the ENTER key without having first keyed any data. The previous entry made from that display console is echoed in the data entry area. The echoed data may be entered by pressing the ENTER key or it may be cleared by pressing the PA2 (CNCL) or CLEAR key.
DOC122 Function not allowed while MIH active
Certain DOCS functions are not allowed while the missing interrupt handler in the supervisor is active. The disallowed functions include PF Key update and comment entry.

These functions will be permitted as soon as the reply has been entered for any outstanding missing interrupt handler messages (0E0n).

DOC123 DOCS logon required
An entry was made at a DOCS console that has not been logged on. The device must first be logged on to DOCS.
DOC124 slu Returned to ACF/VTAM by system operator
An operator action caused a DOCS console that had not successfully logged on to be returned to ACF/VTAM.
DOC125 cuu (RE)loaned to id SYSxxx
The referenced display console was loaned to the partition identified as ID as the programmer logical unit shown. When a device is borrowed by a region/partition that uses physical device addressing (i.e., VTAM), the SYS number will be SYSXXX.
DOC126 cuu returned to DOCS by {operid | id TERM}
The referenced display console was returned to DOCS. If operator-id is included, it means that that operator logged on to the device when the device was loaned to the borrowing region/partition.

If id TERM is included, the device was returned to DOCS because the borrowing task terminated, either normally or abnormally.

DOC127 Hard wait hardwaitcodes
A hard wait has occurred. DOCS have not necessarily caused the hard wait. Traditional methods for determining the cause of the hard wait should be used. The hard wait code, ccc, is shown along with the 1st 24 bytes of absolute storage.
DOC128 Reset cuu
This is an internal message that DOCS uses to return a console to VM if a hard wait occurs.
DOC129 DOCS will expire in nn days
This warning message is displayed as a general broadcast message once per hour when DOCS is due to expire within 15 days.
DOC130 Inquiry reply
An on-line definition was entered without any operands. The current values have been appended to the operator's inquiry. The values shown may be altered and reentered.
DOC131 Auto-reply for id Reset by termination
An operator auto-reply, which was being held by this device, was cleared because the object partition was canceled or reached End of Job.
DOC132 Job stream not sent. IUCVconnect error - Return code = rc
An IUCV connection that was attempted because of a Virtual Machine Id in a job statement failed. The error code returned by the IUCV CONNECT command is indicated in the error message.

This error message is written to the connector machine consoles immediately following the job statement as if it were part of the JOB statement itself. Return codes greater than 10 reflect the actual IUCV return code received by DOCS.

The return code details the following errors:

01
A job stream contained the virtual machine identification of a machine that this machine is already receiving the SYSLOG data from as a secondary virtual machine.
02
A GETVIS error, indicated by a prior DOC411 error message prevented the connection from being established between this virtual machine and the target virtual machine.
11
Target communicator is not logged on.
12
Target communicator has not invoked a DECLARE BUFFER function.
14
Maximum number of connections for target exceeded.
15
No authorization found. The directory for the connectee exceeded.
16
Invalid CP system service name.
17
Invalid function code in IPPCNCD.
18
Value in IPMGLISM.
DOC133 Selected entry
The data line echoed in the input area was selected by positioning the cursor within the specific data display line and depressing the ENTER key. The line may be altered or entered as if the operator had keyed it.
DOC134 Partition is stopped
The partition for which data was entered has been stopped with a $P command. The partition must be restarted with a $G command before data may be entered for the partition.
DOC135 ALLOC cmd invalid with MVAS=NO
When multiple virtual address spaces have been prohibited via the DOCS MVAS configuration definition, any ALLOC command which specifies address space 2 or 3 is overwritten by DOCS by appending the message to the ALLOC command. ALSO, the PAUSE bit is set in every partition's communication region to prevent automatic startup since an addressing exception would occur.

Either remove the DOCS configuration definition MVAS=NO to allow multiple virtual address spaces or correct the ALLOC command.

DOC136 CP command not authorized
Either CPCMD=NO has been specified or the specified CP command requires a class the virtual machine was not authorized for. The command is rejected.
DOC137 AR command rejected; begins with numeric
The input is a command for AR; but it begins with a numeric. There are no AR commands that , begin with a numeric. The command is rejected.
DOC138 cuu unable to return to DOCS
A request was made to return the specified terminal to DOCS, but DOCS is unable to save the terminal's current screen buffer. The request is ignored and the terminal is left on loan.

2xx Prefix

TOP

DOC200 [$x | ?x ] is an unknown inquiry or imperative cmd

The preceding ?X or $X function is not currently supported.
DOC201 Paging in process - pagingcommand
This message is written to a display console in response to a paging command. The paging command entered by the operator is echoed on the initial and subsequent paging requests.
DOC202 Paging complete
This message is written upon completion of the paging function. Completion may be because a full screen of paging data has been written to the display console or because the limits of the hardcopy file have been reached.
DOC203 Paging ignored or discontinued
The last paging or control function is either disallowed because no hardcopy file is in use or the function is discontinued because of an error on the hardcopy file.
DOC204 From [operid | cuu | slu] - message
The detailed message was sent from the specified DOCS console.
DOC205 [operid | cuu | slu] Invalid status
The preceding message was destined for a device address that is not a usable DOCS device or is a DOCS device that is currently not available to receive the message.
DOC206 Hard copy file nn% full
This message details the current capacity of the hardcopy file.
DOC207 Enter = Continue fwd ; PF2 = Continue bwd
The preceding inquiry (?) or imperative ($) command resulted in more reply lines than could be shown on a single screen. The ENTER and PF2 keys may be used to scroll forward of backward through the available reply data. Some reply data will permit the forward of backward function to wrap from the last line to the first line or from the first line to the last line.

The CLEAR or PA2 (CNCL) key must be depressed to exit from the control function.

DOC208 Paging discontinued because of HC file error
An I/O error occurred while paging was in progress. The paging request may be reentered; however, the hardware error will probably persist requiring that the hardcopy file be moved to another device.
DOC209 Num of pages or lines specified is out of range
The preceding paging request specified a number of pages or lines that calculates either beyond the number of records currently in use for a backward request. The lowest and highest record numbers in use on the hardcopy file may be determined by issuing a Page Backward (PB) command and noting the first record number shown in the paging complete message. Then terminate the paging request with the CLEAR or PA2 (CNCL) key. Then issue a page forward (PF) command and noting the first record number shown in the paging complete message.
DOC210 Pf key nn data
The inquiry function ?K with a PF key number was used to retrieve the current value of the canned command for this display console. The data is placed in the data entry line of the display console followed by a underscore character. The data may be altered as desired and restored pressing the original PF key or another PF key. If a PF key is depressed without altering the data, the original data will be stored. The original PF key data is not altered unless the command is stored after being retrieved.
DOC211 Device not originally on loan
The $L command was entered on a display console which was not previously on loan to a problem program.
DOC212 Data compare reset
The Data Compare Facility has been reset.
DOC213 Data compare not active, reset ignored
The Data Compare Facility was not active and either a $D or $S command was entered without any operands.
DOC214 Partition SYSLOG Id invalid as used
A partition SYSLOG Id was specified improperly while trying to activate the Data Compare Facility.
DOC215 Register designation invalid
A general-purpose register was specified as an operand while trying to activate the Data Compare Facility; however, the register designation is invalid.
DOC216 Address value invalid
An attempt was made to activate the Data Compare Facility; however, the address operand contains invalid characters. Only 0-9 and A-F are allowed.
DOC217 Address out of range
The address operand used to activate the Data Compare Facility is beyond the limits of available storage. If an address was supplied along with an exact length, be sure that the specified address plus the specified length minus 1 does not exceed the storage limit of the system.
DOC218 Relative address out of range
The address operand used to activate the Data Compare Facility was specified with a partition SYSLOG Id. The resultant value is outside the range of the partition.
DOC219 Logical operator invalid
The logical operator operand of the Data Compare Facility may be , =, or (less than, equal to, greater than). Each of these logical not ( ) symbol.
DOC220 Data compare argument missing or invalid
The data argument operand for activating the Data Compare Facility either was omitted or does not conform to detailed specifications.
DOC221 Explicit length invalid
An explicit length was specified as an operand for the Data Compare Facility. Either the length exceeds 16 bytes or an explicit length should not be used in conjunction with the other operands that were submitted.
DOC222 Decimal value invalid
A positive or negative value was specified as the data argument for the Data Compare Facility. Most likely the decimal value either exceeds nine digits in length or contains other than numbers (0-9).
DOC223 Binary bit string invalid
A binary bit string was entered as the data argument operand for the Data Compare Facility. The binary bit string may not exceed 32 bits and only valid characters 0,1 and X are allowed.
DOC224 Data compare activated, xxx PSW swap unresolved
The Data Compare Facility has been activated; however, the PSW identified in the message has been swapped and the Data Compare Facility A PSW is considered swapped, if the address portion of the PSW points beyond the end of the supervisor. If the program If the program which swaps the referenced PSW does not handle the PER bit properly, contact the author of that program; otherwise, contact SPI Technical Support.
DOC225 Data compare facility activated
The Data Compare Facility has been activated with either a $D or $S command. The operands may be verified with the ?D inquiry comma
DOC226 Data compare facility req ignored. In use by [cuu | slu]
An attempt was made to activate the Data Compare Facility while it was currently active for the display console identified in the me
DOC227 Address table full
The Data Compare Facility builds a table of PSW addresses, in the system GETVIS area, where the program event recording bit must be
DOC228 Data compare not active
This response to the ?D inquiry command indicates that the Data Compare Facility is not active.
DOC229 Data compare act: [cuu | slu ] addr oper data
This response to the ?D inquiry command indicates that the Data Compare Facility was activated by the display console identified in
DOC230 Loan request rejected, data compare active
The $L command was entered to re-loan the display console to a problem program partition; however, that display console currently has already been re-loaned to an application.
DOC231 Data compare xxxVIS error - Return Code = rc
The Data Compare Facility issues a GETVIS to obtain space in the system GETVIS area during its initialization. 1024 bytes are obtained. FREEVIS is used to release the storage obtained above when the Data Compare Facility is deactivated. If this message indicates that the GETVIS failed, the system GETVIS area is not large enough to accommodate the GETVIS request. The If this message indicates that the FREEVIS failed, the constants saved within the $DOCSCPG phase following the GETVIS have been altered
DOC232 Invalid operator Id: operid
A $B logon command requires that the operator identification be entered beginning in the first position of the data entry area. The operator ID may be from 1 to 8 characters in length and may only contain alphanumeric characters (A-Z and 0-9). Re-enter the LOGON command.
DOC233 Invalid password, 1-8 alphameric char req
The password entered with a $B logon command must contain from 1 to 8 alphanumeric characters. Reenter the logon command.
DOC234 Logon invalid. Console currently in use by: operid
A $B logon command was entered at a display console which is currently in use by the operator identified above. The console must be logged off using the $Z command prior to initiating another logon.
DOC235 $B command must be followed by Operator Id and optionally a password
A $B logon command was entered without any operands. Reenter the logon command followed by the operator identification. If password protection has been specified for this user, the password may be entered along with the operator identification or the operator will be prompted for the password.
DOC236 Operator Id invalid. Logon with Operator Id and password
Operator identification has been specified for the logon procedure. The operator identification must match those supplied at DOCS initialization time. Re-enter the logon command with correct operator identification.
DOC237 Invalid password. Restart logon procedure
An incorrect password was entered. Reenter the logon command followed by the correct password.
DOC238 CMS | LCL | VTM [cuu | slu | user ] Logged onto DOCS [by operid]
This message is written to all display consoles and to the hardcopy file as a general broadcast comment whenever a logon procedure is completed. It indicates that the display console is now available for use with any device characteristics that may have been specified for that operid.
DOC239 CMS | LCL | VTM [cuu | slu | user] logged off [by operid]
The $Z command has been entered at the specified console. The device has had the characteristics that were specified for it during DOCS initialization restored. This message is written to all display consoles and to the hardcopy file as a general broadcast comment whenever a logoff procedure is completed.
DOC240 operid already logged on to [cuu | slu]
The Operator Id supplied in the logon command is already logged on at the device shown in the error message. An operator may only be logged to a single display console at one time.
DOC241 $S not allowed by remote consoles, use $D
The $S (hard stop) format of the Data Compare Facility is not permitted since there would be no way to restart the CPU from the remote location; however, the $D command is allowed.
DOC242 User operid Logoff forced
The DOCSVTAM program was terminated while the named user was still logged on forcing the logoff.
DOC243 id is an invalid partition Id
A $C command was entered with an invalid SYSLOG Id.
DOC244 id is restricted to this dev
A $C command was entered to cancel all or part of the auto-replies in the named partition; however, that partition is excluded from the issuing console.
DOC245 Auto-replies not being held for id
A $C or a RESET command in DOCSUTIL was issued to cancel the partition auto-reply facility for the named partition but there were no auto-replies active in the region/partition.
DOC246 All partition auto-replies for id reset by operid
The named operator reset the partition auto-reply facility for the specified partition.
DOC247 Screen has been rebuilt
This message is issued upon completion of the DSSD and data display areas of a console being rebuilt in response to the $I command.
DOC248 id is not currently logged on
The specified unit is not currently in a logged on status. The logoff command is ignored.
DOC249 id is not a valid console designation
A logoff command was entered and the unit to be logged off could not be identified. The logoff command is ignored.
DOC250 Loan rtrn argument is: argument
The loan return argument currently in use for this console is shown.
DOC251 Per facility currently in use
The Program Event Recording facility of the real or virtual machine is currently in use. Other possible users of the PER facility include SDAIDS and the PER facility when operating under VM.

The current user of the PER facility must be deactivated and the $D or $S command reentered.

DOC252 Screen image frozen & printed on cuu
A $F command was entered to freeze the current contents of the console. If a dump of the screen was also specified, the output device, which contains the dump, is noted.
DOC253 Printer designation invalid
A $F command to both freeze and dump the screen image specified an invalid device. The screen is frozen but the dump request is ignored.
DOC254 Printing discontinued - I/O error - Status = X'ssss', Sense = X'ss'
A screen image dump resulting from a $F command was discontinued because of an I/O error on the printer. The screen will remain frozen until released by the operator.
DOC255 PF key[S] [nn] restored
The specified program function key canned command(s) have been restored in response to a $K command.
DOC256 $K function invalid, ignored
A $K PF key canned command restore function could not be performed because:
  1. An invalid PF key was specified, or
  2. The object of the canned command does not exist for the user profile or device reset profile.
The $K command is ignored.
DOC257 SVA usage = X'nnnnn' bytes from SDL + X'nnnnn' dynamically acquired
The number of bytes of SVA space used by DOCS is displayed at the completion of a ?B inquiry command.

The SDL usage includes the DOCS phases placed into the SVA by SDL commands prior to DOCS being initialized.

Dynamically acquired space results from $DOCS phases not loaded to the SDL as well as dynamic GETVIS storage acquired, and subsequently released, by specific DOCS functions.

DOC258 userid is not a valid virtual machine
The virtual machine named in a $X command is not the identity of a virtual machine. The $X command is ignored.
DOC259 Target Id is not available
A $X command was entered for a DOCS virtual machine which is no longer connected to the entering virtual machine. The entry is ignored.
DOC260 Path to virtual device in use
Another console is in the process of replying to the same outstanding read on the target virtual machine designated by the $X entry. The entry is ignored.
DOC261 id is not a valid partition for $P command
The partition SYSLOG Id specified in a $P command is invalid or the partition is not currently active. The command is ignored.
DOC262 id is already stopped or running real
The partition specified in a $P command has already been stopped or the partition is running a user program in real mode. The command is ignored.
DOC263 id stopped by [operid | cuu | slu]
The designated region/partition was stopped, via a $P command, by the indicated console. This region/partition may be restarted using the $G command.
DOC264 id Restarted by [operid | cuu | slu ]
The designated partition was restarted, via a $G command, by the indicated console.
DOC265 id is not a valid partition for $G command
The partition SYSLOG Id specified in a $G command is invalid.
DOC266 id is not stopped
The designated partition was not stopped with a $P command.
DOC267 id is using the LTA and may not be stopped
A partition may not be stopped when it owns the logical transient area since the results could be disastrous to the remainder of the system.
DOC268 vmid Reply req: id(,id ...)
The partitions on the indicated DOCS virtual machine have outstanding reads.
DOC269 id has attached sub tasks and may not be stopped
A partition may not be stopped if there are subtasks attached to the main task.
DOC270 No match found for: input arg
A ?U inquiry command could not find any I/O devices which satisfied the configuration definitions. The configuration definitions are echoed in this message.
DOC271 ?A requires supervisor Job Accounting support
The ?A inquiry command requires that job accounting support be specified in the supervisor.
DOC272 GETVIS error for ?A - Return Code = rc
The return code shown resulted from a GETVIS for SVA storage required by the ?A function. The size of the SVA must be increased.

The total amount of SVA storage currently in use by DOCS may be requested with the ?B inquiry command.

DOC273 Paging discontinued, rec # X'xxxxxxxx' [UNUSED | CLEARED]
The paging routine has unexpectedly encountered either an unused or cleared record in the hardcopy file. The record number contained within the error message should be noted. Paging may be continued by pressing the ENTER key

This is an indication that the DOCS hardcopy file has been corrupted and DOCSUTIL, in non-diagnostic mode, may terminate prematurely when reading the hardcopy file. The DOCSUTIL LIST function should be used to determine the status of the hardcopy file.

DOC274 USE SPIEXPIR TO RETRIEVE EXPIRATION AND CPU INFORMATION
This message is display as a result of the ?E command. This command is no longer supported. Use the SPIEXPIR program to obtain expire information.
DOC275 id not successfully stopped by $P cmd
A $G command which was issued to restart a partition was ignored since the $P command to start the partition was not successful.
DOC276 $X command not allowed for non-SECDATA device
$X is not allowed for this device.
DOC277 Update not allowed - id
The user does not have read/write access to the named Id.
DOC278 Replid invalid under DOCS. Use ?R command
The REPLID attention routine command is not valid under DOCS. The ?R command performs the same task.
DOC279 operid has attempted an invalid logon, access denied
A logon was attempted but was rejected because the userid and/or password was invalid. The logon procedure must be restarted from the beginning.
DOC280 PF8 = Continue fwd PF7 = Continue top
The preceding ?A command resulted in more lines than could be shown on a single screen. The indicated PF keys can be used to scroll the display.
DOC281 $D SYSTEM requires VSE/ESA Ver. 2 (DOM)
The $D SYSTEM command requires the DOM interface to the Console Router which is only available on VSE/ESA Version 2 and later systems. The request is ignored.
DOC282 SCRMAP for xxxxxxxx not found.
The corresponding entry in the DOCS Master Screen Phase Table could not be located for the terminal used to enter the $D command. The request is ignored.
DOC283 Invalid cursor location for this command
The cursor location was not on a SYSLOG data line or the line was not a high intensity line. The operator must place the cursor on the high line that is to be removed.
DOC284 DOM request not successful
The VSE/ESA system did not set the return code to zero for the DOM request. The request may or may not have been processed.
DOC285 $D Operand is not SYSTEM
An operand other than the keyword SYSTEM was entered with the $D command. The request is ignored.
DOC286W DOCS RECEIVED INVALID MSG DATA BLOCK!
An invalid Message Data Block (MDB) was returned to DOCS by VSE during a Redisplay operation from the VSE Hard Copy file. DOCS has substituted this message for the invalid message returned by VSE.

3xx Prefix

TOP

DOC300 Unable to calc buffer size

The device returned an invalid buffer size. This is probably a hardware error.
DOC301 OUTEXIT phase phasename - not found in the SVA
The phase specified in the OUTEXIT= start-up parameter is no SVA resident..
DOC303 I/O error trying to calc buffer
An I/O error occurred on the display unit while trying to determine the buffer size and device characteristics. This is probably a hardware error

Note: Each of the above error messages is suffixed with the name of the master screen phase that is assumed by DOCS in order to continue operations.

DOC304 Auto-replies not allowed 'buckets' not defined
An auto-reply cannot be stored because during DOCS start-up there was insufficient SVA GETVIS to acquire an auto-reply storage area.
DOC305 Hard copy I/O error
An I/O error has occurred while referencing the hardcopy file. The function that the hardcopy file was being used for is discontinued.
DOC306 Awaiting reply - reason
A screen has been rebuilt and this message is used to denote an outstanding read when the previous data line from the task, which issued a read, is not available from the hardcopy file because of the reason shown. The possible reasons are: After the MIH message has been replied to, a $I command may be entered to rebuild the screen from the hardcopy file.
DOC307 SDAID area too small - nnK additional required
When running in a SHARED=LOW environment, DOCSMAIN could not be loaded because the SDAID area is too small. Enlarge the SDSIZE= operand on the SYS command in the IPL procedure. An SDSIZE=128K is generally sufficient to allow DOCS activation and the use of SDAIDS.
DOC308 Output exit 'phasename' loaded at X'address'
The OUTEXIT definition has been specified in the DOCS startup definitions. This message shows the load address and name of the phase.
DOC309 Bad return code from Common Interface R15=value
DOCS was unable to communicate with the SPI Common Interface. Ensure the SPI Common Interface is active before starting DOCS.
DOC310 Initialization failure in DOCSVXD - Routine=nn, RC=nn
DOCS was unable to establish Vendor Exits for CLASS = DOC. The request which failed is indicated by the Routine number and the reason is indicated by the Return Code. Possible values for Routine and their meanings are
01
PRODID CHECK - For Product SPI/DOCS
02
PRODID DEFINE - For Product SPI/DOCS
03
PRODID DELETE - For Product SPI/DOCS
04
PRODID AUTH=YES- For Product SPI/DOCS
05
PRODID CHECK - For DOC(MSG)
06
PRODID CHECK - For DOC(CMDREP)
07
PRODEXIT DEFINE - For DOC(MSG)
08
PRODEXIT DEFINE - For DOC(CMDREP)
09
PRODEXIT ENABLE - For DOC(MSG)
10
PRODEXIT ENABLE - For DOC(CMDREP)
11
PRODEXIT DISABLE - For DOC(MSG)
12
PRODEXIT DISABLE - For DOC(CMDREP)
13
PRODEXIT DELETE - For DOC(MSG)
14
PRODEXIT DELETE - For DOC(CMDREP)
DOC312 Unrecoverable tape I/O error - filename 1st record nbr = X'record'
An unrecoverable error has occurred on the specified tape file. The operator is prompted for a reply. Valid replies are
SKIP
Will cause the input block in error to be skipped.
IGNORE
Will result in the error indication being ignored and the block in error being used as is.
RETRY
Will cause the I/O operation to be retried.
EOF
Will terminate the input history file at its current position as if end of file had been reached.
Should an unrecoverable input error result in the cancellation of DOCSUTIL while it is clearing the hardcopy file, DOCSUTIL may be rerun at any time since it does not open the hardcopy file until the input history tape has been completely copied.
DOC313 nnn Records on input file - nnnnnnnn
This message indicates the number of logical records read from the history tape.
DOC314 nnn Records on output file - nnnnnnn
This message indicates the number of logical records written to the new history tape.
DOC315 DOCSUTIL padding record
When DOCSUTIL is clearing the hardcopy file, it is sometimes necessary that it cause used records to be placed in the remainder of the first block on the hardcopy file. These padding records are for control use only and may be ignored.
DOC316 Unknown sa dump tape
The DUMP function of DOCSUTIL does not recognize the stand alone dump tape assigned to SYS006.
DOC317 GETVIS request for nnnK failed RC=X'nn'
The DUMP function OF DOCSUTIL attempted to acquire the specified amount of GETVIS. The return code indicates the reason for the failure. DOCSUTIL must be run in a larger area.
DOC318 SYS006 is an invalid device for dump function
The DUMP function program issues this error message when SYS006, in the region/partition where the program is running, is assigned to an unsupported device type. SYS006 must be assigned to a stand alone dump tape or unassigned to cause the dump to be formatted and printed. This facility assumes that DOCS is operational.
DOC319 DOCS not located in dump file
This error message is issued by the DUMP function when the resident portion of DOCS cannot be located. The DUMP function examines the first four bytes pointed to by the address of CRTTAB in SYSCOM. When DOCS is operational, these four bytes contain the core mark 'DOCS' followed by the base address of DOCSMAIN.

When DOCSMAIN cannot be located via the normal addressability technique shown above, the DUMP function will attempt to locate the resident portion of DOCS by scanning for embedded core marks. If DOCSMAIN still cannot be located, processing is terminated.

If SYS006 is unassigned, this message indicates that DOCS is not running. If SYS006 is assigned to a stand-alone dump file which is acceptable, the message indicates that DOCS could not be located in the system for which the dump was taken.

DOC320 SYSCOM could not be located
SYSCOM could not be located on the stand-alone dump tape. The tape may need to be processed with the VSE utility DOSVSDMP.
DOC321 Unable to locate address X'nnnnnnnn' on dump file
The dump function could not locate the specified address. Process the dump tape using the dump utility and contact SPI Technical Support.
DOC322 Dump file contains DOCS version v.m.p, DOCSDUMP at level v.m.p
The DUMP function cannot format the dump file on SYS006 since the dump program is at a different version / modification level than the dump file. Catalog the proper level of DOCSDUMP to the core image library.
DOC323
This is a prompt to enter a pair of addresses for the beginning and ending areas to dump.
DOC324 Invalid reply for addr addr,addr
The address pair entered as a reply to the above message was invalid. The address pair is shown.
DOC325 Addr list table full
The number of address pairs submitted in response to message 065 exceeded the capacity of the address table. All subsequent entries are ignored.
DOC326 Unable to locate BG COMREG
The DUMP function was unable to locate the background partition communication region. An attempt is made to find the communication region of another partition. As a result, some of the formatted tables may be incorrect.

Some versions of DOSVSDMP overlay the background partition communication region when the dump routine itself is IPLed. The dump function can resolve this internally and format the tables without error.

DOC327 SYSCOM addr in low core invalid
The address of SYSCOM at location X'80' was not usable by the DUMP function. An attempt is made to calculate the address of SYSCOM. The reason why the address of SYSCOM was destroyed at location X'80' should be investigated.
DOC328 Program check within the dump function at +nnnnn DOCS storage will be printed
A program check occurred within the formatting routine in the DUMP function. This normally will occur when a control block within DOCSMAIN has been overlaid.

The DUMP function will discontinue trying to format any additional control blocks and will print a storage dump of the DOCS related storage areas.

DOC329 Selection table entry should be 0. Device Index = nn. Selection control list = X'xx'
This message is issued by the DUMP function when an inconsistency between control blocks is encountered and is intended as a diagnostic for SPI Technical Support.
DOC330 Selection control byte for = nn indicates empty slot (X'xx').
This message is issued by the DUMP function when an inconsistency between control blocks is encountered and is intended as a diagnostic for SPI Technical Support.
DOC331 Data suppression table corrupted at addr X'addr'
The data suppression table for a device or a profile has been corrupted. Please contact SPI Technical Support.
DOC332 Unable to release pages - Return Code = rc
An internal error has occurred while releasing virtual pages. Please contact SPI Technical Support.
DOC333 Which includes nnK extra for mult virt addr spaces
When VSE/SP permits multiple virtual address spaces, the beginning of BG real and virtual must be rounded up to a segment table boundary (64K) resulting in additional storage being allocated to the Fx area built by the DOCS initiator.

If multiple virtual address spacing is not going to be used, this extra storage may be eliminated via the DOCS MVAS configuration definition.

DOC334 CPJCL parameter contains restricted classes
One or more classes of CP commands specified in the CPCMD definition are restricted from this virtual machine. The CP classes specified in the VM directory entry are assumed. Correct and resubmit the CPCMD definition.
DOC335 SYSIPT not assigned
The DOCS initiator was executed from SYSRDR and SYSIPT was not assigned or it was executed within an ASI procedure and the procedure was cataloged without a DATA=YES statement. The DOCS initiator will continue without any user definitions.
DOC336 definition - partition & system parameters must precede device & Profile parameters
The definition indicated in the message is out of sequence. The correct sequence for configuration definitions is detailed in the DOCS documentation.
DOC337 DOCSUTIL FUNCTION=LIST has completed.
This message indicates the normal completion of a List function job in which the online hard copy file was listed and/or archived. It is also used to position the hard copy file when the New option is specified.
DOC338 nnn occurrences of scan argument found
This is a diagnostic message and is intended for SPI Technical Support.
DOC339 Phase phasename not found. Cannot continue execution
DOCSUTIL attempted to load one of its sub-programs and was not able to locate the named phase. DOCSUTIL execution terminates. ensure that the proper libraries are being searched and that the LNKEDT portion of the installation procedure completed with no errors.
DOC340 nnnK more storage needed to load phase phasename
The size of the region/partition is too small to load the named phase. Increase the size on the EXEC statement by the specified value.
DOC341 Enter [UTIL | LIST | RPLY | DUMP | EOJ] command or HELP
This message appears when DOCSUTIL has been executed from the console or if DOCSUTIL has canceled. Enter a valid command or HELP.
DOC342 SYSIPT parameter table exceeded
DOCSUTIL reads all of the definition statements from SYSIPT and stores them in a table before processing. This table has been exceeded. Decrease the number of definition statements and re-run the job.
DOC345 Unknown function - 'function'
A FUNCTION command was specified with an invalid function name. Function name must be one of the following: DUMP, EOJ, LIST or REPLY.
DOC346 nn Statement(s) skipped due to errors
'nn' is the total number of statements in error encountered during the execution of DOCSUTIL.
DOC347 Invalid command - 'command'
The named command is invalid. Command processing continues with the next definition statement.
DOC348 Auto-reply accepted for id
When executing DOCSUTIL, FUNCTION=REPLY from the console, this message signals that the previous AUTO-REPLY has been successfully stored into the region/partition.
DOC349 Scan table exhausted
The internal table that stores the scan information taken from INCLUDE/EXCLUDE commands has been exceeded. Decrease the number of INCLUDE/EXCLUDE commands and rerun the job.
DOC350 Missing or unpaired parentheses
Multiple scan arguments were specified in an INCLUDE/EXCLUDE command without enclosing the arguments within parentheses or a right or left parentheses is missing.
DOC351 Too few operands
Required operands are missing from the previous command.
DOC352 Invalid scan type - 'scantype'
The named scan type operator in the INCLUDE/EXCLUDE command is invalid. Refer to the DOCS documentation for additional detail on the INCLUDE/EXCLUDE commands.
DOC353 Invalid conditional operator - 'operator'
The named conditional operator in the INCLUDE/EXCLUDE command is invalid. Refer to the DOCS documentation for additional detail on the INCLUDE/EXCLUDE commands.
DOC354 Missing or unpaired quotes
The previous command contained data that needed to be enclosed within single quotes or single quotes were unpaired.
DOC355 Length exceeds maximum of 64 characters on reply-keyword
The previous auto-reply contained keyword or reply data that exceeded the maximum of 64 characters.
DOC356 Invalid date or time - 'date/time'
The date or time in the previous INCLUDE/EXCLUDE command is invalid. Refer to the DOCS documentation for a description of coding conventions.
DOC357 Invalid input parameter - 'parameter'
The named value is invalid for the INPUT configuration definition. The INPUT operand must be DISK or TAPE.
DOC358 Invalid job name - 'jobname'
The previous INCLUDE/EXCLUDE command contains a JOB scan argument that is invalid. Job names must be 1-8 alphanumeric characters in length.
DOC359 Invalid Id - 'id'
The named Partition Id is invalid. The Partition Id must be a generated partition in the supervisor (i.e., BG, F1-Fn).
DOC360 Invalid sort parameter - 'parameter'
The named SORT definition is not one of the following: DATA, JOB or PARTITION.
DOC361 Invalid output parameter - 'parameter'
The named OUTPUT definition is invalid. The OUTPUT definition must be DISK or TAPE.
DOC362 Invalid archive parameter - 'parameter'
The named ARCHIVE definition is not ACCUMULATE or NEW. Refer to the LIST function subcommand for additional information.
DOC363 nnnn
This is an informational message used by the HELP command.
DOC364 Hardcopy file has been formatted
The hardcopy file has just been formatted. This message appears at the end of the format process if there were no errors.
DOC365 Formatting hardcopy file - Enter 'PROCEED' to continue
The hardcopy file is about to be formatted. Enter 'PROCEED' if you wish to continue the format process. Any other response will cancel the format process.
DOC366 Formatting canceled
The format process has been canceled and the hardcopy file will not be formatted. This message is issued if the response to DOC365 was anything other than PROCEED'
DOC367 Invalid TAPEIN/TAPEOUT parameter - 'parameter'
The named TAPEIN/TAPEOUT definition is not CUU (channel unit address) or SYSXXX (valid logical unit).
DOC368 Assign for 'cuu' failed - reason
The MSAT macro failed to complete the assign for 'cuu'. The reason can be one of the following:
DOC369 Unexpected return code from macro macro, RC=x'rc'
The named macro received a return code indicating that an error has occurred while accessing the VSE hard copy file. The DOCSUTIL job will be unable to continue processing.
DOC370 Invalid disposition - 'disp'
The DISPOSITION definition is invalid for one of the following:
DOC371 Invalid pos parameter - 'pos'
The POS definition is invalid for one of the following:
DOC372 Invalid format parameter - 'parameter'
Indicates an invalid format for one of the following:
DOC373 GETVIS failure for auto-reply RC=rc
An attempt was made to store an auto-reply into the system GETVIS area but a GETVIS macro failed with return code shown. Refer to the GETVIS macro documentation for additional information.
DOC374 Id parameter is required
Upon entering auto-replies using the operator to DOCS communications facility (* DOCS REPLY=), the ID definition must be specified to indicate which region/partition to which the auto-reply applies.
DOC375 Number of replies exceeds maximum of 200
The maximum of 200 auto-replies per partition has been exceeded.
DOC376 Id of 'AR' not valid for online auto-reply
The ID definition must be a valid region or partition (i.e., R1-RF or F1-Fn).
DOC377 Statement out of sequence - statement
An ENDREPLY command was entered before a REPLY command. The REPLY command along with any optional sub-commands (KEYWORD, POS, DISPOSITION, CLASS and ID) must be specified before the ENDREPLY command.
DOC378 Invalid CLASS or DYNCLASS parameter - parameter
An auto-reply parameter specified with CLASS= or DYNCALSS= is invalid. The parameter may only be a single alphabetic character.
DOC379 Invalid SPAN parameter - 'parameter'
Only YES or NO may be specified for SPAN. If SPAN=NO is specified, unused auto-replies are cleared at EOJ (/&). If SPAN=YES is specified, unused auto-replies will be retained for the next job to use.
DOC380 Auto-reply nnn for id reset by operator
The named operator reset the sequence number auto-reply in the region/partition shown. This is a general broadcast message that goes to all consoles that have COMMENT=YES specified.
DOC381 Class 'c' auto-replies reset for id by operator
The operator, for the named region/partition, has reset the named class of replies. This is a general broadcast message that goes to all consoles that have COMMENT=YES specified.
DOC382 id is restricted Id, [Auto-reply not loaded | Command not processed | Reset ignored]
The named region/partition is restricted from the user/device. The user/device must have read/write access to the region/partition before auto-replies can be processed
DOC383 Reply security is active, 'user' parameter required
RPLYSEC=YES was specified at DOCS initialization time and a userid and optional password must be provided before any auto-replies can be stored when running DOCSUTIL.
DOC384 User/password invalid
The length of the USERID or PASSWORD exceeds 8 characters.

DOC385 DOCSHC cannot be opened - reason

The hardcopy file is not available for processing for one the indicated reason. Possible reasons are:
DOC386 Abnormal termination intercepted
The partition in which DOCSUTIL is running has been canceled. A STXIT AB intercepts the cancellation.
DOC387 Pgmchk in program at +nnnnnn, Code code - reason
A program check has occurred within DOCSUTIL. Please contact SPI Technical Support.
DOC388 Invalid reset parameter - 'parameter'
The RESET sub-command must be one of the following:
DOC389 Must be running under VM to issue CP commands
The CP command of DOCSUTIL is only valid when running under VM.
DOC390 DOCSUTIL, FUNCTION=[DUMP | EOJ | LIST | REPLY], INVOKED AUTOMATICALLY
The named function is being automatically invoked by one of the DOCS batch utilities that was explicitly executed. This facility is provided for compatibility purposes.
DOC391 HC file being cleared/formatted, function cannot be interrupted
While clearing or formatting the DOCS hardcopy file a 'MSG id' was entered for the region/partition in which DOCSUTIL was running. Interruption of a CLEAR or FORMAT operation would result in the hardcopy file being partially cleared. The CLEAR or FORMAT operation will continue to completion to allow the pointers within DOCSMAIN to be reset to the beginning of the hardcopy file.
DOC392 Invalid command - Cannot flush, cancel or msg the DOCSUTILpartition
The entered command entered has been rejected because it would affect the currently active DOCSUTIL partition.
DOC393 Diagnose command at +X'nnnn' failed, Interrupt Code=X'nnnn'
An error has occurred during initialization while trying to issued a DIAGNOSE command. Copy the message number and contact SPI Technical Support.
DOC394 SVA GETVIS for SHARED=LOW failed, RC=X'rc'
An SVA GETVIS request failed while trying to initialize DOCS. The return code is detailed under the GETVIS macro.
DOC395 PFIX for phasename failed, RC=rc
A PFIX request for DOCS SVA phase 'phasename' has failed. The return code is detailed under the PFIX macro.
DOC396 phasename has been PFIXED
A PFIX request for DOCS SVA phase 'phasename' has completed successfully.
DOC397 Unable to locate IUCV external buffer, DOCS will declare one
Beginning with VSE/SP 4, an IUCV buffer was declared during IPL by the supervisor. DOCS attempts to locate this buffer and use it. IF DOCS cannot locate a buffer, one is declared.
DOC398 Plus nnnK of PFIXED SVA storage at address
When running an ESA mode supervisor, DOCS displays the amount of storage that DOCS acquired from SVA GETVIS for control blocks and work areas.
DOC399 Id and DYNCLASS parameters are mutually exclusive
In the REPLY function of DOCSUTIL, the ID and DYNCLASS sub-commands cannot be specified together. Remove one and then re-run the job.

4xx Prefix

TOP

DOC400 Accepted

The program to DOCS command was successfully executed.
DOC401 Rejected
The program to DOCS command was rejected. This will generally occur when an option is to be set and the condition of that option program command is inconsistent with the command.

For example, issuing the program command DOCS EOJLOG=NO when EOJLOG=NO is already in effect would cause REJECTED to be placed in the program command data line.

DOC402 Unknown
A problem program issued an unrecognized command. This may be the result of a SYSLOG data line being written with 'DOCS' in the first four positions that in actuality should not have been intercepted by DOCS. If this is the case, the reply is ignored.
DOC403 Unchanged
A program to DOCS or operator to DOCS command resulted in no change to the specified option.
DOC404 INV-FUNC
A program to DOCS or operator to DOCS command is invalid. The request is ignored
DOC410 No available selection list entries - DEV= Too small
A virtual machine, other than the virtual machine where DOCS is running, attempted to reply to an outstanding read which DOCS sent to it and DOCS is unable to build a Device Control Block to process the entry.

The responding virtual machine may reissue the response since a Device Control Block may have become available.

If this message appears frequently, adjusting the value in the DEV definition should increase the number of selection list entries in DOCSMAIN.

DOC411 GETVIS error for IUCV entry - Retn Code=rc
A GETVIS was issued to obtain space from the SVA for a Device Control Block. 'rc' is the return code set by the supervisor.

If this error message was issued as a result of an SMSG reply being issued to the DOCS virtual machine, the SMSG entry is ignored.

DOC412 Reply to target-id part-id Not authorized & ignored
A virtual machine sent an SMSG command to a virtual machine with an outstanding read; however, the virtual machine with the outstanding read (the target of the SMSG command) had not designated the sender as eligible to send the reply to the outstanding read.
DOC413 SMSG source & target may not be same virtual machine
The VM/370 SMSG command was used to attempt to reply to an outstanding read on the same virtual machine where the read occurred.

Either correct the virtual machine name where the reply data was to be sent if the read is on another virtual machine, or use a DOCS console on the specified guest machine to reply to the outstanding read.

DOC414 VM-ID id Awaiting reply via [CP SMSG | DOCS $X] cmd
This message is written on the target virtual machine console indicating that a read is outstanding on the machine indicated by the VM ID at the end of the data line for the region/partition indicated. The read may be replied to using the option identified in the message.

When the target virtual machine is a DOCS machine, the reply is entered via the DOCS $X command. When the target virtual machine is not a DOCS machine, the reply is entered via the CP SMSG command.

DOC415 Connect req to connectee from connector not authorized
The virtual machine identified as the connector attempted to send data to the virtual machine identified as the connectee but this path is not authorized in the connectee's VM directory entry.

The data will be sent via the CP MSGNOH or MSG command. If this is a desired path, the IUCV statement in the connectee's VM directory entry should be changed.

DOC416 [Message | Warning | Error message | Informational message] Received from userid
One of the above IUCV types of data has been received. This is an informational message. The actual message appears within the data display area of the console. This message may be suppressed via the CPALERT definition.
DOC417 Connect not allowed -- vmid is already connected
An attempt was made to connect to a virtual machine as a secondary user but a connection already exists between DOCS and this guest. The request is ignored.
DOC418 Error sending data -- connection to vmid terminated
DOCS encountered an error trying to send data to a VM SECUSER. DOCS has severed the connection.
DOC419 CP command not processed, GETVIS failed RC= rc
DOCS was unable to issue the requested CP command because it could not acquire GETVIS storage. The decimal value of the return code is displayed.

5xx Prefix

TOP

DOC500 Unexpected Retn code FLWG name at +nnnnn. RF-R1 = xxxxxxxx

ACF/VTAM has set an unexpected error coded in response to a manipulative macro which was not anticipated. Please contact SPI Technical Support.
DOC501 DOCS not operational
DOCSVTAM was executed without DOCS being operational. This might occur if the core mark 'DOCS' followed by a fullword containing the base address of DOCSMAIN is not located in the first 8 bytes of CRTTAB in the supervisor. Please contact SPI Technical Support.
DOC502 DOCSVTAM currently executing in id
DOCSVTAM may only run in one partition at a time and it was found to be active in the specified region/partition.
DOC503 Unable to open ACB. Return Code = rc
The Open for the ACF/VTAM ACB failed. The reason for the failure is shown as the 2 digit return code set by the Open. Refer to the proper ACF/VTAM publications for a description of the OPEN return codes.
DOC504 Error in initial setlogon, R0 = xxxxxxxx RF = xxxxxxxx
The error detailed in registers 0 & 15 was returned in response to the SETLOGON macro.
DOC505 Unable to handle logon request. Device limit of nn exceeded
A remote device attempted a logon to DOCS but all of the available entries in the DOCS device control block address list are occupied. The logon request is rejected.

Increase the value in the DEV definition to allocate additional device address list entries.

DOC506 [GET | FREE]VIS error. Return Code = rc
A GETVIS or FREEVIS failed. A GETVIS failure indicates that insufficient space exists in the GETVIS area where DOCSVTAM is running. Either increase the region/partition size or reduce the value in the SIZE= operand of the EXEC statement for DOCSVTAM.

A FREEVIS failure indicates an internal program error in DOCSVTAM and should not occur. Please contact SPI Technical Support.

DOC507 OPNDST failure. SLU = sluname
The OPNDST issued in the LOGON exit in DOCSVTAM was unsuccessful. The logon attempt is rejected. Generally this will result from an invalid logon mode table specification for the device.
DOC508 DOCSVTAM v.m loaded at X'xxxxxxxx'
This informational message is issued by DOCSVTAM when it is executed. The DOCS PTF level is display on message DOCS029 or may be obtained using the $B or DOCSAPAR commands.
DOC509 Invalid CCW chain in device ctrl blk
An internal error has occurred and the device control block for a remote console has been corrupted. The device control block will be reconstructed and normal operations will resume. This is a severe error and should be reported to SPI Technical Support.
DOC510 VTAM is not operational
DOCSVTAM has been executed but ACF/VTAM is not currently running. ACF/VTAM must be operational before DOCSVTAM may be executed.
DOC511 DOCSMAIN & DOCSVTAM at different levels
The named phases are at different version/mod levels and therefore are incompatible. Be sure that mixed core image libraries have not caused this condition.
DOC512 LERAD Exit SLU Name = sluname RF-R1 = xxxxxxxx xxxxxxx Displ=+nnnn RPLREQ=xx RPLFDBK=xx
ACF/VTAM has passed control to the LERAD exit routine in DOCSVTAM. Registers 15, 0, and 1 along with the displacement in DOCSVTAM of the function, which caused entry into the LERAD routine, the RPL request code and the feedback data from the RPL, are detailed.

This condition should not normally occur as it indicates a logic error within DOCSVTAM. Contact SPI Technical Support for assistance.

DOC513 EOJ requested by system operator
The system operator requested termination of DOCSVTAM via the OC (Operator Communication) STXIT routine in DOCSVTAM or by an ACF/VTAM command that has requested DOCSVTAM to terminate. End of Job will occur as soon as all remote consoles are dequeued.
DOC514 [No | nn] units will automatically be dequeued
End of job has been requested with the number of remote consoles specified still active. These consoles will be dequeued by DOCSVTAM after being logged off.
DOC515 Enter applid if other than "DOCS"
DOCSVTAM allows the operator to supply the Application Id, the same value specified on the APPL statement in the DOCSVTAM.B source library member. If no value is entered, DOCS is assumed.

By permitting the operator to supply the Application Id, DOCSVTAM may operate in a cross domain environment.

By executing or attaching the phase DOCSVTAU rather than DOCSVTAM, the operator prompt will be bypassed and the APPLID of DOCS will be used if the installation has not created a DOCSVTNM phase.

DOC516 RU size of nnn too small for sluname, Min value = minvalue
The PLU maximum RU size specified in the session parameters (bind area) is too small for DOCSVTAM to handle. The minimum RU size that DOCSVTAM can handle is shown.
DOC517 Trace entry - routinename comment +addr r14,, r15.. r0.. r1..
This message, which appears on SYSLST only, represents a trace line produced by DOCSVTAM when the first UPSI bit is set when DOCSVTAM is initiated.
DOC518 DEV= missing or too small
The DEV definition must be specified to cause the DOCS initiator to reserve address space for remote consoles. Refer to the DOCS documentation for detailed information.
DOC519 Invalid recovery action return code = X'rc', RPL addr =X'addr'
ACF/VTAM returned the recovery return code to DOCSVTAM for the RPL located at the designated address. The recovery return code was not recognized by DOCSVTAM.
DOC520 Logon attempt by slu was from an invalid LU type X'xx'
The LOGON exit in DOCSVTAM received control with a logon attempt from the secondary logical unit shown. This secondary logical unit type is not supported by DOCSVTAM.
DOC521 Response error from slu - FDBK = X'xxxxxx', Sense = X'ssssssss'
The RESP routine in DOCSVTAM received control from ACF/VTAM with the physical error designated by the feedback bytes and input sense bytes.

A description of these fields will be found in the appropriate ACF/VTAM manuals.

DOC522 Your terminal type unsupported by DOCS
Same as message DOC520 except that this message is sent back to the terminal which attempted the logon.
DOC523 ACB for applid being opened
This is an informational message issued prior to the OPEN for the DOCSVTAM ACB being issued.
DOC524 Logon request from slu rejected. DOCSMAIN resources exhausted
Insufficient resources were reserved when DOCS was initialized to accommodate an additional device control block. This is generally an indication that the DEV parameter should be increased.
DOC525 DOCSVTAM initialization complete
This is an informational message that indicates that the DOCSVTAM initialization function is complete and that logon to DOCSVTAM may begin. DOC525 may be used as a keyword argument for submission of auto-replies to ACT/VTAM that are to follow DOCSVTAM activation.
DOC526 DOCSVTAM may not run in address space nn
DOCSVTAM must run in either the same address space as ACF/VTAM or in a shared space. DOCSVTAM must be executed in another region/partition or must be attached to ACF/VTAM as a subtask using the:

F NET,ATTACH

ACF/VTAM command.

DOC527 SPIIF CALL=IFADDR failed.
A call to the SPI Common Interface to request the address of the SPIIFDCT failed. The utility program or sub-task is terminated. Ensure that the SPI Common Interface is installed and is active.
DOC528 SPIIFSVA is at level 'v.m', need 4.2 or later.
Release 7.2 of SPI/DOCS requires Release 4.2 or later of the SPI Common Interface. The utility program or sub-task is terminated. The level of the active Common Interface module is displayed in the message as 'v.m'. Install the correct version and it will become active following the next IPL.
DOC529 To terminate DOCSVTAM/U, reply "y".
An AR MSG command request to terminate the batch version of DOCSVTAM or DOCSVTAU was made and the operator must reply as indicated for the termination to continue. Any other reply, including an EOB, will result in the termination request being ignored.

6xx Prefix

TOP

DOC601 function Function failed. Unable to continue

An IUCV QUERY command failed. This message is usually preceded by a DOC602 message that describes the reason for the failure.
DOC602 description
This message provides a description of the cause of an IUCV QUERY command failure.
DOC603 Connection severed by userid
The guest machine (userid) has severed the DOCSCMS IUCV connection, typically by entering a $R command.
DOC604 TIMEOUT - connection-type did not occur.
DOCSCMS was unable to make the IUCV connection to the target guest machine for the specified reason..
DOC605 DOCS/CMS ABEND -- REASON UNKNOWN -- SEE DUMP
A DOCS/CMS error has occurred producing a CMS dump. Please contact SPI Technical Support.
DOC606 QUEUEING ERROR -- SEE DUMP
A queuing error has occurred. Please contact SPI Technical Support.
DOC607 DOCS/CMS ABEND -- PROGRAM CHECK type AT addr -- SEE DUMP
A program check has occurred at the address indicated. Please contact SPI Technical Support.
DOC608 ERROR error ISSUING command function COMMAND AT addr
The indicated error was issued by the command function at the address shown. Please contact SPI Technical Support.
DOC609 DOCS/CMS REQUIRES option
The indicated option is required for the proper operation of the DOCS/CMS program. Correct the problem and re-try.
DOC611 RECEIVE BUFFER TOO LARGE FOR STORAGE -- SEE DUMP
Please contact SPI Technical Support.
DOC614 DOCS/CMS REVISION revision-level
This message is in response to the DOCS $B command and shows the version level of the DOCS/CMS program.

7xx Prefix

TOP

DOC701 XPCC FAILURE, FUNC=X'nn', RC=X'nn',REASON=X'nn', ADD=+X'nn'

This message is issued when an XPCC communications macro fails. Record all information and contact SPI Technical Support.
DOC702 [GET|FREE]VIS FAILURE FOR POWER FUNCTION - RC=X'nn'
A GETVIS or FREEVIS macro failed for the specified return code. For a GETVIS failure, the return code can be found the VSE Messages and Codes publication. For a FREEVIS failure, contact SPI Technical Support.
DOC703 SPOOLER NOT AVAILABLE OR HAS TERMINATED
The system SPOOLer was not fully initialized or has terminated. The entered command is passed to the attention routine.
DOC704 nnnnnnnnnnnnnnnnnnnnnnnnnnnn (xxxx)
A return code of 4 received after an XPCC communications macro. Record the information and contact SPI Technical Support.
DOC705 MSG FROM SPOOLER
This message displays the return message from the system SPOOLer after the command was entered on the command line.
DOC706 UNKNOWN ERROR CODE - RC=X'nn', FDBK=X'nn', DD=X'nn'
An unknown return code was received after an XPCC communications macro. Record all information and contact SPI Technical Support.
DOC707 UNKNOWN ACTION COMMAND
An invalid action command was entered into the first field of a POWER queue display. Valid commands are:
DOC708 nnnnnnnnnnnnnnnnnnnnnnnnnnnn (xxxx)
A return code of 8 was received after an XPCC communications macro. Record the information and contact SPI Technical Support. '(xxxx)' is the displacement within the service routine.
DOC709 'AR' OR SPOOLER IS RESTRICTED TO READ ONLY
An attempt was made to modify a queue member when the operator is READ restricted to that particular class, or a command was entered on the command line and the region/partition or attention routine is restricted.
DOC710 INVALID COMMAND ON COMMAND LINE
An invalid command was entered on the command line.
DOC711 DATA NOT FOUND
A SCAN command was executed, but the search argument could not be found in the queue member.
DOC712 ACCESS DENIED - OPERATION ABORTED
An attempt was made to delete or modify a queue member in a particular class that the operator is read restricted. The operation is canceled. Access is controlled via the PWRQ, INCL and EXCL definitions.
DOC713 OPERATION ABORTED BY OPERATOR
The operator pressed PF3/PF15/PA2 while an operation was in progress. The operation is canceled.
DOC714 FATAL ERROR PROCESSING VTOC OPEN RC=rc
A OVTOC open request has failed with return code 'rc'. The return code is documented under OVTOC in Volume 4 of the VSE Diagnostic Reference Manual (see CVH Return Codes).
DOC715 FATAL ERROR PROCESSING VTOC READ RC=rc
A PVTOC read request has failed with return code 'rc'. The return code is documented under PVTOC in Volume 4 of the VSE Diagnostic Reference Manual (See CVH Return Codes).
DOC716 FATAL ERROR PROCESSING VTOC CLOSE RC=rc
A CVTOC close request has failed with return code 'rc'. The return code is documented under CVTOC in Volume 4 of the VSE Diagnostic Reference Manual (see CVH Return Codes).
DOC717 INVALID OPTION SPECIFIED
An invalid options was specified for the function. The indicated option must match one of the options shown at the top of the screen.
DOC718 VTOC ERROR DURING FREEVIS RC=rc
A FREEVIS request has failed with the indicated return code. Refer to the VSE Messages and Codes manual for detailed information.
DOC719 VOLSER IS DOWN OR NOT FOUND RC=rc
The DOCS DVTOC command was unable to process the request because the volume specified was not found or off-line.
DOC720 ERROR LOCATING LABEL AREA RC=rc
A LABEL(LOCGRPL) request failed with the indicated return code 'rc'. Refer to the VSE Messages and Codes manual for detailed information.
DOC721 ERROR READING LABELS RC=rc
A LABEL(GETNXL) request failed with the indicated return code 'rc'. Refer to the VSE Messages and Codes manual for detailed information.
DOC722 FREEVIS ERROR IN LABEL ROUTINE RC=rc
A FREEVIS request has failed with the indicated return code. Refer to the VSE Messages and Codes manual for detailed information.
DOC723 STORAGE UNAVAILABLE TO PROCESS VTOC
There was not enough work storage to process the volume request. The work storage may be increased by:

If not specified, the default storage size is 4K.

DOC724 FREEVIS ERROR IN APAR ROUTINE RC=rc
A FREEVIS request has failed with the indicated return code. Refer to the VSE Messages and Codes manual for detailed information:
DOC725 FATAL ERROR INVALID APAR BIT MAP
The APAR bit map table used by the DOCSAPAR command is invalid. The table is constructed during DOCS initialization from the phase DOCS$A. Display the contents of the phase and then contact Software Pursuits Technical Support.
DOC726 INVALID TYPE MUST BE T FOR TEMP OR P FOR PERM
The value entered in the TYPE: field of the DOCS LABEL DISPLAY screen must either be T for Temporary (to display Partition User Labels) or P for Permanent (to display Partition Standard Labels). Correct the value and press ENTER.
DOC727 INVALID PARTITION MUST BE VALID PARTITION OR STD
The argument entered for the DLAB command, or the value entered in the PARTITION: field of the DOCS LABEL DISPLAY screen was invalid. It must either be STD (for System Standard Labels) or a valid two character partition/region id (for Partition Labels). Correct the value and press ENTER.

8xx Prefix

TOP

DOC801 Invalid Request in REDisplay mode.

The entered command is not valid while you are in REDISPLAY mode. You must exit from redisplay and then re-enter the command.
DOC802 MGCRE Unexpected Result - RC='rc', RS='rs'.
The Return and Reason codes displayed were returned from an MGCRE call to pass a command to the IBM VSE/ESA Version 2 system, but they are not a normal or expected response. The condition is treated as successful and DOCS attempts to continue processing.
DOC895 session terminal session suspended. Function canceled.
This message is issued from Page Back or Initial Screen Build and indicates that the DOCS screen will be returned to the SYSLOG display.
DOC896 HCF Intercept Error - PSW=psw INTCD=xxxxxxxx.
The DOCS Hard Copy File Intercept task has detected an error that has resulted in a program check or abend in the Hard Copy File task. The failing PSW and Interrupt Code are displayed. This message is followed by an AR SHOW command that displays an 88-byte storage area containing additional data relating to the error. The Hard Copy File task is re-activated and processing continues.
DOC897 Suspended terminal session 'session' has been reactivated.
This message is issued when VSE suspends a DOCS console session. DOCS will reactivate the session and processing continues.

  1500 Fashion Is. Blvd., Suite 205
San Mateo, CA 94404
Phone: 650-372-0900
Fax: 650-372-2912

Copyright © 2000 by Software Pursuits, Inc.
All rights reserved