SPRI Release 3.7 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
• 0xx Messages
• 1xx Messages
• 2xx Messages
• 3xx Messages
• 4xx Messages
• 5xx Messages
• 6xx Messages
• 7xx Messages
• 8xx Messages
• 9xx Messages

Introduction

This publication is a complete compilation of all messages that apply to the SPI/SPRI product.

To facilitate use, this publication lists all messages in alphabetical order using the message prefix. Messages are shown under each prefix in numeric order.

Message Format

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

SPRInnn[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 Messages  

This is an informational message only. The location indicated has just read a $SPL$CMD statement containing a SPRI command or a user has submitted a command under program control. The text of the command is reported in this message.

This message results from an attempt to:

• Reference a unit record device for which your Location ID is not authorized, or
• To use a command restricted to a location with operator privileges.

This message may occur even if the command is entered by the console operator. Refer to the SPRIDEFN 'LOCATION' statement, and CPUID OPERID= statement for security concerns.

This message occurs when a CANCEL DISPLAY command is entered during the processing of a display command, or the SPRIDEFN message file is full. The display is immediately terminated.

This message is issued to the operator as a warning that a report is generating more lines than were estimated. The program creating the report is running in the region or partition named by loc. The message will be repeated each time the estimated lines is exceeded by another twenty percent. If the job is a test it is possible the program is in a loop and is erroneously generating lines. If this is suspected, ask for assistance or cancel the region indicated in the message.

This message is issued when an error has occurred on one of the unit record devices used by SPRI. The type of error is indicated by the message text and sense (SNS) information. CCSW indicates the command code of the failing CCW and the CSW associated with the error. 'loc' indicates the device having the error. The types of errors generally encountered are:

• Command Reject
• Bus Out Check
• Equipment Check
• Data Check
• Device Not Operational

After this message is issued, the device must be stopped then started before processing can resume on the device.

This message is issued after a command has been entered requesting the re-positioning of a report on a printer or punch, or when system restart data is received for a 3800 type device. Another message will be issued when the positioning is complete. Until that time, only a cancel command will be accepted for the device. The cancel command will immediately terminate any positioning in progress.

The statement displayed is in error. Check the format of the statement and the operands/options entered. Re-enter the statement in the proper format.

The device address entered in the SPRI command is not defined or is the wrong device type. Check for syntax error or a device missing from your IPL procedure or SPRIDEFN control statements.

The device named by loc has been freed as the result of a command entered to SPRI. No further work will be selected by the device until a new SELECT command is entered for the device.

This message is issued when there is a change in the Form Name, 3800 flash frame name, or 3800 burster-trimmer use. The user may supply extra text for this message from the Report Separator routine to describe a Form Name. Form changes can only occur when a SELECT command is issued for a printer or punch without a Form Name specification. The operator should mount the requested form, flash frame, or thread or unthread the burster-trimmer. After the requested action has been completed the device should then be stopped (if not already stopped) then started to indicate the form change is complete.

An alternate method to indicate that the form change is complete is to issue a 'START cuu' command. The latter technique is required for RJE printers.

A CANCEL command was entered for the named device. This message indicates the cancel operation has successfully completed and the current copy of the report has been satisfied.

The device indicated has run out of work to process and awaits new work to enter the queue. When new work arrives, the device will restart itself automatically. Generally the most convenient time to change form is after a printer has gone Idle.

The program reading from the reader in the named region has run out of input. Note that this is data being read by a program, not Job Control reading JCL. The /* was probably missing from the end of the data cards for the program. Provide more input to the program, allowing it to continue automatically or use the Attention Routine to cancel the Job.

This message is made in response to a command to SPRI that has no other way of directly indicating to the operator that the command was processed. This message is merely confirmation that the requested action has taken place.

This message is used to indicate to the operator that the requested function has been recognized and the action is pending. When the requested action has completed a confirmation message will be issued.

The device indicated has been in the 'Intervention Required' status for more than one minute. This message is issued as a reminder that the device should be readied. This message will be repeated at one minute intervals until the condition is corrected.

SPRI has detected that the timer is not incrementing properly. SPRI requires the timer to balance its operations and to make index entries unique. If the timer is turned off, then reactivate the timer.

The PAGES operand was specified for the SPLIT command but, because the report was in the CREATE status, the operand could not be used and was ignored.

A SPRI request has been made which is not valid. The originator of the request is named by loc. Refer to the documentation for the needed function.

UPSI 1111 was present when SPRIDEFN was executed. A "Y" reply will open SPRIDEF as an output data set and destroy any previously existing data set. This must not be done with SPRI active or with another CPU using the definition data set. A reply of "N" opens the definition data set for input and no damage occurs. SPRI may be active and the definitions shared if the reply is "N".

This prompt can be eliminated, forcing an input open, by changing the UPSI statement.

An unrecoverable I/O error has been encountered on the SPRI definition data set. Have the hardware repaired or move the data set to a different location.

This message is issued by SPRIDEFN when an attempt is made to reference the SPRI definition data set before it has been created. Specify UPSI 1111 and execute SPRIDEFN again.

An attempt was made to delete a CPU definition, or change a CPUID while the named CPU was active. You can not change or delete an active CPU definition. The input statement is ignored.

The value specified for the named operand was invalid and the value was left unchanged. Check for required numerics and review the list of valid operands for the operand. If the value must be changed, a new run of SPRIDEFN will be required. The input statement is ignored.

The operand named is required but either an illegal value was specified or the operand was omitted. The entire control statement, with any continuation statements associated with it, is bypassed and ignored. The control statement with corrected operands will probably need to be re-submitted.

A statement has been rejected by SPRI because two or more operands were in conflict. Check the statement and correct the conflicting operands. The statement is rejected and ignored.

The SPRIDEF data set is too small to hold the definitions submitted. The definition data set must be re-created with a larger extent. The Job is cancelled.

The name of the Index data set must always be specified. The Index must exist prior to any reference to its name. The index name may be a maximum of seven characters in length. If a reference is made to a non-index data set, the statement will also be rejected. The statement is rejected and bypassed.

This message is output on the console to inform the operator that a warning message has been issued by the SPRIDEFN program. This alerts the operator to read the SYSLST report output by the program to determine the nature of the errors. Correct the statement in error and rerun SPRIDEFN.

SPRI has received a valid PSTART response record from an external device application.

An external device application has rejected a PSTART order for the indicated device. The reason that the device was not started in indicated at the end of the message.

An external device application has rejected a command for the indicated device. The reason for the rejection is indicated at the end of the message.

A device (loca) has been stopped by the indicated location (locb). This is an informational message. If the location that stopped the device is SPRI then the most likely cause is a broken XPCC connection. No action is required.

An attempt has been made to start a device. The subsystem was not specified or a default was not available. The command to start the device is ignored. You must specify a subsystem name if a default is not defined with a SPRIDEFN PRINTER statement.

An SNA Signoff command was received from loca which is not an SNA/RJE workstation

A VSE/Power link session failed. The return and feedback codes are set by VSE/POWER in the XPCC control block used for this session.

This is an information message only and indicates that the partition or region is idle.

This message is issued when all disk space available to the data areas associated with named index are full. The spool system is unable to accept any more requests to spool reports out to these data areas. All tasks attempting to spool output to this area simply wait until disk space becomes available and then automatically re-start themselves. Disk space only becomes available when reports are purged from the spool files, which normally happens several minutes after a report has finished printing. To obtain more queue space, print reports and purge those which are not needed.

This message is issued only after the message SPRI081W has been issued. The spool system has obtained more disk space for the data areas associated with the named index and has resumed spooling output. No operator intervention is required.

The index named has been completely filled and an attempt has been made to add a new directory entry to the data set. Batch processing may stop in one or more regions until index space is again made available. In order for normal processing to resume, many entries may have to be purged. Review the directory status and purge unneeded entries.

If this message appears, the Index data set is too small and should be re-created with a larger extent when possible.

Directory space is now available in the named data set. Previous processing that was suspended due to a full directory is now resumed. No further action is required by the operator.

The specified blocksize exceeds that allowed for the named Index data set. The specified block size is ignored.

The extent data set being created is too small. Increase the size of the data set extent.

The SPRI command entered has been terminated without finishing its requested function.

A Data Area or Index area has been destroyed and requires re-creation. See S403: SPRI Customization and Programming guide for instructions on how to recreate the SPRI files.

An index is being created and it has no associated Data Area. The VARY command is rejected.

The reader, region or partition specified by loc has no SPRI index and therefore no data area in which to spool lines. Issue a VARY command to bring an index on-line or a RDRDEF or REGNDEF command to name an index to be accessed by the reader or partition.

An INDEX= operand specifies an index name that was not defined to SPRI when it was activated. The operand value is ignored.

The named job accounting data set has exceeded the specified WARNFULL= value and is nnn% full. If 100% full, job accounting records are discarded and ignored.

Use the JOBACCT command to offload the accounting information to tape.

The requested index is not on-line or is not defined to the system. If the index name is properly spelled you may need to issue a VARY command to bring the index on-line.

The data areas associated with the named index has exceeded the specified WARNFULL= value and is nnn% full. If the data areas become completely full, spooling will stop until additional space is made available. The percentage reported may not be completely accurate for a shared index. However the DISPLAY DISK command will correct the percentage reported.

The problem is generally related to:

1. A program that is creating a large volume of output because of a loop, etc. Check what jobs are processing and compare them with any large elements in the index. Take actions as indicated by your installation.
2. A greater than normal use of spool space. This is generally caused by large output from month-end, quarterly, or annual processing that is relieved when output is processed.
3. Printers/punches being free and not processing output as would normally be the case. Check the devices and begin processing your output to relieve the problem.

Print or purge reports to make additional space available.

This is a warning message to indicate that the SPRI Master Definition data set has reached the indicated precentage of capacity. SPRI will attempt to add the information to the data set providing it is not at 100%. This message is generally caused by: An attempt to define additional SPRI master definitions, or the excessive use of the DISPLAY command to send displays to remote locations. If your installation will be using a large number of messages, the data set should be increased.

If the data set is 100% full, SPRI will discard messages that will not fit into the data set. The PURGE MESSAGE command may be used to temporally clear the data set of unwanted messages.

An error has occurred while using the XPCC facility. The actions where this type of error may occur are:

• IDENT
• CONNECT
• RECEIVE
• REPLY
• SENDR

Contact Software Pursuits Technical Support and inform them of the message and the actions that led to the error.

The indicated SPRI index has exceeded the specified WARNFULL= value and is nnn% full. The message is displayed with each 1% increase.

An XPCC device connection failed to properly connect to the indicted subsystem. Check to be sure the proper subsystem is being specified and that the correct sequence of commands is being used.

The JOBACCT command has been issued and the Job Accounting data set is not on line.

1xx Messages  

This message is presented during SPRI activation to indicate those unit record devices that were not assigned to SPRI because no definition was found in the definition data set for the devices during SPRI activation. In some installations some devices are kept from the spool system in this fashion. None of the devices listed will be available to the spool system.

This message is presented at SPRI activation to indicate those unit record devices that were attached by SPRI but in the DOWN status. A SPRI UP command will be required for these devices before they can be accessed. Combination reader/punch devices will be listed twice.

An attempt has been made to activate SPRI before the master definition data set has been created. It is also possible that this data set has been destroyed. Use SPRIDEFN to recreate the definition data set.

More memory must be allocated to SPRI or the configuration must be changed. SPRI105I indicates the amount of memory required.

The SPRI activation routines have been loaded and have begun execution. The current release and PTF level are indicated.

This information message should help in optimizing the memory requirements for SPRI. MVT/VSE systems may change the real memory used with the DEFINE MAXREAL= statement. Use ALLOCR for DOS/VSE and VSE/SP systems. For VSE:ESA systems use SETPFIX LIMIT= statement. Additional memory above the optimum reported, may be desirable if many XPCC applications are used. Excessive memory may increase paging activity. The region type may be:

• CURRENT
• MINIMUM
• OPTIMUM

The current CPU has not been defined to SPRI. This message should be followed by SPRI159D.

An index is being brought on-line with a VARY command. Busy index entries for the named CPU will be reset in the following manner. Elements in the CREATE status will be placed in the PURGE status with a minimum retention of at least two hours. If a user check point was recorded then the element is placed in DISP=X status. Busy reader queue elements will be placed in DISP=X status. Busy PRT or PUN queue elements will be reset to their original disposition unless special DISP=Y (hold on failure) was requested.

The index being varied on-line is busy on the CPU named. No action is required.

The OPT=RECLAIM request on the VARY command has been ignored. Multiple CPU environments need to periodically perform a reclaim by deactivating all CPUs normally. Then start up a single SPRI system with OPT=RECLAIM specified.

Note: This is not the same as JOB/SEQ number reclaim.

The phase name specified in the SPRIDEFN MSTRDEFN control statement for the name of the reader exit, report separator or EXPRESS table was not found. The exit or phase will not be used. This may also be issued as a result of a PLOAD command. Check to verify the phase name and location of the phase. The library must be available to SPRI.

This message is issued during SPRI activation to report approximate positions of reports on printers and punches when SPRI was last deactivated. The position reported is within 150 pages.

An attempt was made to activate SPRI when it was already active. Activation is terminated.

This is an activation information message only. Job Numbers and Sequence Numbers are being validated as an index is being brought on-line. This process should normally take less than 2 minutes.

Note: This is not the same as VARY OPT=RECLAIM.

This is an activation information message only. This indicates a report was in the process of being created when SPRI was last using this index. The element will be placed in the PURGE status with a 2 hour retention, or held with a DISP=X if a user checkpoint was taken.

This is an activation information message only. The reader element was being read when SPRI was terminated. The element is placed in the DISP=X status.

This is an activation information message only. The element was being output when SPRI was last terminated. Busy Routing Codes are reset as if the element was never processed. If hold on PRINT/PUNCH failure was requested then the element is placed in DISP=Y status.

This is an activation information message only. Data space is being reclaimed due to OPT=RECLAIM on the VARY command. The length of time to complete a reclaim is a function of your Data Area size. Large Data Areas may take a long time.

An attempt was made to vary an index offline. The command is rejected because the index is currently in use by the indicated location (loc).

A SPRI command has been ignored.

SPRI has been activated and is ready for activity.

Auto activation is in progress and the commands on SYSIPT are being processed. These commands are executed as if entered by the console operator.

This message indicates that manual activation is in progress and the commands on SYSIPT are being bypassed. Each statement on SYSIPT will be displayed on the console, but no action will be taken on the statements. UPSI 1 indicates manual activation.

All the commands on SYSIPT have been read and processed.

An attempt was made to VARY an index on-line that is in use by another CPU and the index is not defined as a shared index. If there is no other CPU, use the CPU= operand of the VARY command to clear this condition.

The subtask named was not attached to SPRI because the UPSI setting at activation was wrong. Although SPRI can function without the subtask, its use prevents certain deadlocks and improves performance.

The SPI common interface must be active before any SPRI phase can execute. Make sure the needed interface phases are in the SVA, then execute SPIIFACT to activate the interface.

This message is informational only and is issued when an index is placed on-line. If the VARY command is issued from the SYSIPT command stream during SPRI activation, the new job and sequence number counts should be zero.

This message is issued to indicate that the CPU indicated is also active and accessing the SPRI queues.

This message is output to both the console and SYSLST to assist Software Pursuits in determining the cause of a SPRI cancellation. The cancel code is the operating system cancel code. CODE=24 indicates that SPRI was cancelled by the operator.

SPRI is terminating abnormally and needs to output a dump. Enter the cuu address of a real printer or tape drive where the dump may be output. Tape output is preferred if the dump is to be forwarded to Software Pursuits. Additional messages will precede this message to describe the cause of the abnormal termination. Copies of the messages will be output with the dump to the printer or tape. If a null reply is supplied to this message, no dump is output.

The response to message SPRI130D was not the cuu name of a printer or tape in the DVCUP status. Enter a new cuu device name.

This message is provided to describe the cause of a SPRI abnormal termination. This information is generally only useful to the Software Pursuits technical support staff. LOCATION= names the current phase and perhaps a displacement in that phase. The ERROR CODE= value is an internal code that may describe a forced cancel when SPRI detected an internal error. ROUTINE= may specify a SPRI subroutine that detected the error.

This message could be issued for an index, a data area or the MSTRDEFN data set. In a shared system, another CPU has a lock on the indicated data set. If the message includes RC=nn then this is the return code from the LOCK macro. If the CPU that issued the lock has gone down, the AR UNLOCK command can be used to clear any locks.

A request has been made to SPRI that applies to a region that has not been defined.

A request has been made to SPRI that applies to a JOB that is not active on this CPU.

A request has been made to SPRI that applies to a JOB for which there are multiple entries. Repeat the request, but add a Job Number specification to further qualify your request.

A $SPL$CAN card has been encountered for a submission. The entire element being created is discarded.

An attempt has been made to vary the indicated index on-line. The sequence number shown was found to be damaged. The damaged element is purged or truncated. Contact Software Pursuits Technical Support and inform them of the situation.

This message may be issued during SPRI initialization. It indicates that a phase could not be located in the SDL. The SPRI system continues with initialization. The indicated phase may be required for SPRI High Performance operations. As a result, the High Performance operations are disabled

This message is issued in conjunction with message SPRI139W. It indicates that the SPRI High Performance routines have been disabled due to the missing phase indicated in SPRI139W.

Insufficient GETVIS space is available for the operation of the $JOBACCT phase for job accounting. No additional processing is done.

Insufficient virtual storage was available for extended buffering. The return code indicates the problem cause:

01

A return code of 12 was returned from 'CDLOAD' for SPRIFAST indicating insufficient virtual storage was available.

02

SPRIFAST could not obtain enough virtual storage for the buffer.

03

SPRIFAST could not load the anchor table (IJDANCHX).

04

A return code of 16 was returned from 'CDLOAD' for SPRIFAST.

Your installation has exceeded the number of allowed RJE lines under the Software Pursuits RJE Graduated RJE Line schedule. Contact Software Pursuits for additional information.

This message is output when attempting to activate SPRI with a different CPU serial number than the one last used for the CPUID 'x'. 'yyyyyy' was the last CPU serial number that activated SPRI for CPUID 'x', while 'zzzzzz' is the current CPU serial number. If the CPU identified by 'yyyyyy' no longer exits or is inactive, reply "Y". Otherwise reply with "N" to cancel SPRI.

If you attempt to activate two systems with the same CPUID, you will destroy all SPOOL queues and the SPRI Definition Data Set.

Phase $$BSPRIG was not found in the SVA. SPRI does a soft rename of $$BSGMNT and $$BSPRIG in order to process the SEGMENT macro. Do not attempt to use the SEGMENT macro until this error has been corrected. Ensure that $$BSPRIG is loaded into the SVA.

Informational message issued at startup concerning the amount of partition GETVIS. Total= is the amount allocated to the partition. SPRI= is the amount used by SPRI. Avail= is the amount still available for other use.

Informational message that is issued when attempting to start SPRI by entering a // EXEC SPRIROOT job control statement through the console. All commands needed to start SPRI must now be entered via the console.

The TRACESIZE= parameter is required on the trace command. The TRACESIZE= parameter specifies the size of the internal trace table to be allocate. The value is in number of entries. The command is ignored. Reenter the command with the required parameter.

SPRI has exhausted its supply of sequence or job numbers and will now wait for more to become available. Numbers can be made available by purging unneeded queue elements or by properly reclaiming the job and sequence numbers during SPRI activation. See S403: SPRI Customization and Programming Guide for instructions on how to reclaim these numbers.

An attempt was made to issue a VARY command for a disk dataset that was not an index. Use the VARY command for SPRI index datasets only.

This message is issued as a result of a VARY command that required no action for completion.

During initialization after a SPRI abend, SPRI will attempt to clean up its queues by deleting partial or damaged queue elements. This message informs you as to which queue elements are being deleted.

An improperly formatted DXN or an invalid DXN has been read. Job name (xxxxxxxx), sequence number and origin id identify the damaged queue element. The part of the DXN (directory extentsion block) which is bad is indicated by the TYPE= value:

• CIU - Control Intveral Used
• DCT - Data Control block
• DXN - Directory Extentsion
• MAN - Manifest Entry

The TYPE of error will be needed by SPI for diagnostic purposes. The queue element will be deleted.

The SPRI AR command hook looks for the VOLUME command in $IJBAR. This command could not be located and SPRI can not activate its attention routine command hook. Contact Software Pursuits for assistance.

SPRI could not establish it attention routine hook and therefore the attention routine commands are not available. See previous message for cause of the error. Contact Software Pursuits for assistance.

During initialization SPRI hooks into the SGXECB routine in order to allow the SPRISUBF subtask to issue XECB calls. SPRI could not find the SGXECB routine and therefore could not establish its hooks. SPRI will initialize and run without XECB support.

During initialization SPRI hooks into the SGXECB routine. SPRI could not find one of the required hook locations. If this was the first time SPRI was activated after the IPL then the XECB support will not work. If this was a later activation of SPRI then every thing is probably OK. SPRI will initialize and run without XECB support.

During initialization SPRI hooks into the SGXECB routine. SPRI located the SGXECB routine but could not determine which release it was working with and therefore could not establish its hooks. SPRI will initialize and run without XECB support.

The CPU definition record was not found in the definition file. In order to add a default CPU definition for the serial number shown enter a CPUID or CANCEL.

SPRI requires that there be at least one reader defined to the supervisor and to SPRI. SPRI activation is cancelled. Supply the required reader definition.

2xx Messages  

During initialization SPRIJCLE calls the common interface to locate SPIIFDCT. SPRIJCLE received a non-zero return code from this call. Contact Software Pursuits for assistance.

During initialization SPRIJCLE loads SPRIJCLT. SPRIJCLE received a non-zero return code from this load request. Check the return code for the LOAD macro in the appropriate macros manual.

SPRIJCLE received a non-zero return code from a GETVIS macro. Check the return code for the GETVIS macro in the appropriate macros manual.

During initialization SPRIJCLE could not determine which version of the VSE supervisor was active. Contact Software Pursuits for assistance.

During initialization SPRIJCLE could not find JBCSW4. Contact Software Pursuits for assistance.

SPRI's Network Communications Facility has been activated. SPRI networking feartures require that NCF be activated.

NJE node node-name specified in a PSTART command was not found in the SPRI definitions. The node is not started. Verify that the proper node-name was specified in the PSTART command and reissue the command or; update the SPRI definitions with an NJE node definition for the specified node.

Command not processed because node nodename is being stopped. The node is being stopped due to a previous PSTOP command, the remote node initiated a stop or a communications or system error occurred.

Command not processed because node nodename has not been started or is not signed on. Issue the PINQUIRE command for the node to determine its status.

A PSTART command was issued for a node that has already been started. Issue the PINQUIRE command to determine the status of the node.

A PSTART command was issued for an NJE node, but VTAM is not yet active. When VTAM is activated the NJE initialization will complete.

node currently active

The specified node was previously activated.

NJE ACB not open

The VTAM ACB used by NJE is not currently OPEN.

Not if SPRIDEFN's

The specified node was not found in the SPRI definitions.

You can verify the available definitions with a DISPLAY DEFN=NJE command.

Command not processed because node node-name is in auto restart state and has not completed sign-on. This is probably due to inability to establish a session with the remote node. Check return code in message SPRI267I to determine why the session cannot be established.

The specified queue member was successfully transmitted to the indicated node using transmitter number TRn.

The transmission of the specified queue member has been cancelled. The DISP= parameter indicates the disposition of the element following the cancel action. The values are:

K/D

Element returned to 'ready' status.

H

Element placed in 'hold' status.

P

Element placed in 'purge' status.

The specified transmitter or receiver on the indicated node is terminating.

• xx is either TR for transmitter or RV for receiver.
• n is the specific transmitter or receiver task number.
• yyy indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

The specified transmitter xxn-yyy on node node-name cannot be activated because the total number of In-Service transmitters would exceed eight. One of the In-service transmitters will have to be drained to activate the specified transmitter.

• xx is either TR for transmitter or RV for receiver.
• n is the specific transmitter or receiver task number.
• yyy indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

A PACT command was issued for a transmitter or receiver that is currently In-Service.

• xx is either TR for transmitter or RV for receiver.
• n is the specific transmitter or receiver task number.
• yyy indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

NJE task xxn-yyy specified in a PDRAIN or PFLUSH command was not found in node node-name control blocks. This is an internal SPRI error. PSTOP the node with the EOJ option and then PSTART it to re-initialize the node control blocks. Please report this error to Software Pursuits, Inc.

• xx is either TR for transmitter or RV for receiver.
• n is the specific transmitter or receiver task number.
• yyy indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

NJE task xxn-yyy specified in a PDRAIN or PFLUSH command is not In-Service on node node-name. Issue a PINQUIRE for node node-name to determine task status.

• xx is either TR for transmitter or RV for receiver.
• n is the specific transmitter or receiver task number.
• yyy indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

NJE task xxn-yyy specified in a PDRAIN or PFLUSH command was not active on node nodename. If the command was PDRAIN the task is set to drained/out-of-service status.

• xx is either TR for transmitter or RV for receiver.
• n is the specific transmitter or receiver task number.
• yyy indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

A full RJE license is required in order to activate a NCF subsystem. This includes NJE, SNA/RJE and APPC functions. Contact Software Pursuits in order to acquire a license.

An NJE command could not be processed because ACF/VTAM is terminating.

The local system attempted to establish a session with node nodename. The session cannot be established. The RC field contains the SSENEI (yy) and SSENSMI (xx) codes returned from VTAM. The system will continue to retry the connection every 15 seconds. This message will be displayed at one minute intervals. Ensure that a PSTART command for the local node has been issued at the remote node.

The local system attempted to establish a session with node nodename. The request failed. The PSTART process is terminated. Ensure that the cross domain connection is established to the remote system and a PSTART has been issued at the remote node. Then retry the PSTART command. Contact SPI technical support if the error condition persists.

NJE cannot be initialized. Refer to preceding NJE message to determine the cause.

The NCF VTAM operating system sub-task has abnormally terminated. Dump the SPRI region and contact SPI technical support.

NJE node node-name is attempting to establish an NJE session with the local system. The remote node has not been started on the local node. Issue a PSTART command for the remote node to establish the NJE session.

The local system has successfully established an NJE session with remote node nodename. Job streams can now be transmitted between the two systems.

The NJE session with remote node node-name has been terminated. The system will attempt to automatically reestablish the session if it was terminated due to a remote node PSTOP command or a session communications failure. The reason for the termination is defined by the RC field. The field can have the following values:

• RC=00 - Local PSTOP command issued
• RC=02 - Remote initiated quiesce stop (PSTOP PNET,nodeid,EOJ)
• RC=03 - Remote initiated immediate stop (PSTOP PNET,nodeid)
• RC=04 - Communications error
• RC=05 - NJE system error

Please dump SPRI and contact SPI technical support if an NJE system error is identified.

An error was detected during initialization of the Network Communications Facility. Initialization cannot continue. This message is preceded by a message that gives the reason for the failure. This is usually a SPRI or VTAM definition error.

NCF has successfully terminated. All resources used by the NJE function have been released.

A command was submitted for SNA/RJE or NJE and it cannot be processed because the function is not active.

Resources are still allocated for the NJE function. This condition should clear and message SPRI275I should appear. NJE termination can be forced by issuing a PSTOP,,IMM command. Please take a dump and contact SPI technical support if the PSTOP command fails.

An internal error has been detected in the NCF function. All other SPRI functions should continue normally. At a convenient time please take a SPRI dump and contact SPI technical support.

This message indicates a NJE internal error. Please take a SPRI dump and contact SPI technical support.

An invalid NJE buffer was received from node nodename. The buffer violates NJE protocol rules. The node will be stopped immediately.

• RC=00: NJE receiver received an invalid RID while processing SYSIN/SYSOUT data.
• RC=01: Received RID contained invalid RCB value.
• RC=02: Received a NJE record for node not signed on.
• RC=03: Received a Sign-On record for node currently signed on.
• RC=04: Received a NJE record for an inactive receiver.
• RC=05: Stream Control Record received out of sequence.

An NJE buffer was received that was addressed to a receiver task that was not active or had not sent 'permission granted'. This is an NJE protocol violation. The node will be stopped immediately.

An NJE internal buffer error occurred. Please take a SPRI dump and contact SPI technical support if the error condition persists.

The NJE task xxn-yyy at node node-name has been cancelled and drained. This task must be activated by a PACT command before it can be used for transmission or receipt of job streams. The drain action was taken due to a PDRAIN command being issued or a transmitter task was not allowed to transmit because the corresponding receiver at the remote node was not In-Service. The status of the queue element being processed is:

Transmitter tasks

the element is returned to the spool in ready status (Disp=D/K). If the PDRAIN command specified the EOJ option the element is placed in purged status following successful transmission.

Receiver task

the element is purged.

xx

is either TR for transmitter or RV for receiver.

n

is the specific transmitter or receiver task number.

yyy

indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

The NJE task xxn-yyy at node node-name has been cancelled due to; an immediate node stop action or receipt of a transmitter or receiver cancel record from a remote node during job stream transmission. The indicated task remains In-Service and is available for use. The status of the queue element being processed is:

Transmitter tasks

the element is returned to the spool in ready status (Disp=D/K). If the PDRAIN command specified the EOJ option the element is placed in purged status following successful transmission.

Receiver task

the element is purged.

xx

is either TR for transmitter or RV for receiver.

n

is the specific transmitter or receiver task number.

yyy

indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

The NJE task xxn-yyy at node node-name has been cancelled due to a PFLUSH command being issued. The task remains In-Service and available for use. The status of the queue element being processed is:

Transmitter tasks

the element is returned to the spool in ready status (Disp=D/K). If the PDRAIN command specified the EOJ option the element is placed in purged status following successful transmission.

Receiver task

the element is purged.

xx

is either TR for transmitter or RV for receiver.

n

is the specific transmitter or receiver task number.

yyy

indicates if it is a SYSIN(JOB) or SYSOUT(OUT) task.

This message is displayed following node sign off if the automatic restart function is active for the node and a PSTOP was not issued locally. The node has been reset to the same state that exists following a PSTART being issued. Once sign-on is successful a JOB and OUT transmitter will be started and all receivers will be available to receive new job streams.

An NJE command could not be processed because the NJE function has not been started. The only NJE command that is valid is PSTART.

The NJE interface to ACF/VTAM has been initialized. The SPRI NJE application has been successfully connected to VTAM. This connection will be maintained until the last NJE node is stopped.

The NJE connection to VTAM failed. NJE initialization is terminated. The RC= and ERRF= fields contain data returned from VTAM defining the error.

The NJE connection to ACF/VTAM cannot be established because VTAM is not initialized. NJE initialization is terminated.

NJE termination could not successfully close its connection with ACF/VTAM. Fields RC= and ERRF= contain data returned defining the error. NJE termination will continue.

NJE or RJE termination has successfully closed the connection with ACF/VTAM.

A Z NET,QUICK command was issued to ACF/VTAM. The NJE connection to VTAM is terminated. All NJE nodes will be stopped immediately and NJE will terminate.

A Z NET command was issued to ACF/VTAM. This will cause NCF to terminate. All connected nodes will be stopped after any active job stream transmissions have completed. No new job stream transmissions will be started. The NJE function will be terminated.

VTAM or SNA function request function failed for node nodename. Fields RC= and FDBK2= contain data that specifically defines the error. Node nodename will be stopped immediately. If the AUTO=RESTART option is in effect the system will attempt to reestablish the connection The values for the function request field are:

• GENCB - Error issuing GENCB.
• CLDST - Error issuing CLSDST.
• SHOWCB - Error issuing SHOWCB.
• TERMSE - Error issuing TERMSESS.
• FMH4RJ - Invalid FMH4 sent or received. RC=X'FF', FBBK2=X'FE' means local node reject; RC=X'FF', FDBK2=X'FD' means remote node reject.
• NONSCB - USERFLD contains invalid NSCB; internal error.
• OPNDST - Error issuing OPNDST.
• OPNSEC - Error issuing OPNSEC.
• RPLBAD - Corrupted RPL processing FMH4: internal error.
• SENDPR - Error issuing positive response for FMH4.
• SESSIC - Error issuing SESSIONC.
• SHOWCB - Error issuing SHOWCB.
• DFASYE - DFASY exit error.
• ICNTRL - Invalid SNA control request received in SCIP exit.
• LOSTTR - LOSTERM exit entered.
• RECEIV - Error in RECEIVE.
• SEND - Error in SEND.

An explanation of the values in the RC= and FDBK2= fields can be found in the VTAM programming documentation.

A signon record was received out of sequence.

Node node-name sent a buffer either smaller than 300 bytes or larger than 32K.

Node node-name did not send the correct password. The specified node will not be activated.

3xx Messages  

An element in the SPRI queues which is compacted has been scheduled to be transmitted by NJE. NJE cannot transmit compacted files.

This message in only displayed at an SNA/RJE workstation. The positioning request submitted by an SNA/RJE workstation operator is complete

This message is only displayed at an SNA/RJE workstation. A positioning error has occurred. The positioning information entered by the workstation operator for device/task xxxx was incorrect. The Job and Sequence Number fields define the element affected. The element has been placed in hold status.

The attempt to start NJE or SNA/RJE failed because no SPRI CPU definition entry exists for the CPU. Correct the SPRI definitions and retry the start command.

The attempt to start NJE or SNA/RJE failed because a required parameter in the SPRI CPU definition is missing. Correct the CPU definition entry and retry the command.

This message is received when you attempt to alter an attribute of an element for which you do not have authorization. The entered command is ignored.

This message is the result of attempting to access a queue element for which you do not have authorization. The offending command is ignored.

This message is used for those messages that are sent via a broadcast facility. The sending location is noted at the front of the message.

A command was entered for a device that was not in ready status. This is generally caused by attempting to process on a device that is not available. Check the device and ensure that it is ready to process jobs.

A reposition request has been made and the scan string or the position has not been found. The report remains at the same position.

This message is issued if a command is issued for a device that is already active with some work and cannot accept the new command. A report re-positioning command cannot be entered until any prior report positioning commands for the device have completed. A START or SELECT command will be rejected if a report is already active on the device. Use of OPTION=NEXT on the SELECT command will allow new selection information to be specified even though a report is active.

The report specified by the START command was not found. The sequence number specified did not match any report element for the device. Note that printer reports cannot be started on the punch and punch reports cannot be started on the printer.

The report specified in the START command was found using the Sequence Number specified and is in the process of printing or being positioned for printing.

The report specified in the START command cannot be started because the report is not in the proper state.

A report positioning command or START command has specified a position outside the report segment. The position request must use page and line numbers relative to an unsplit or unsegmented report.

The command contains operands that refer to both reader queues and output (printer/punch) queues. Only one type of queue may be indicated in the command. This message may also be issued if mutually exclusive operands are specified. Review the operands allowed for the command just entered. The command is rejected.

The command entered requires that the device be busy with a report in order for the command to be valid. The device indicated has no active report.

This message is issued to indicate that a 'cancel reset' has completed. The report Sequence Number is displayed and the position of the report. If the report is on a punch, the card number is indicated.

A SNA/RJE workstation has already activated the maximum number of devices for the station. No more devices will be activated (started) for the workstation.

This message is issued when a FREE command is entered for a device that is already in the FREE status.

Report positioning has completed for a report that was being re-positioned by a command from the operator. Printing or punching actually begins when this message is issued.

The command entered does not contain sufficient information to determine if reader or output queues should be affected. Both types of queues cannot be affected in the same command. The operands PRT, PCH or RDR may be added to the command to qualify the type of queue to be affected.

The VARY command has been issued for an invalid index data set. The data set is either misspelled or is not defined. No action is taken.

An attempt was made to open one of the SPRI data sets and the attempt failed. Explanatory messages precede this message.

A request has been made in the specified region/partition to change a Location Id. The console operator can permit or disallow the request. Once a "Y" reply is provided, the question will not be asked again until the next program is executed in the region.

An AUTOSTART has been submitted for the requested region and SPRI is unable to start the region because it is already active.

A DISPLAY or QUEUE command has terminated because the number of lines in the display is greater than the maximum number of lines specified in the DLINES= operand of the command. A specification of DLINE=0 will prevent the display from being interrupted.

A VARY command has been rejected when attempting to bring an index on-line. The blksize for each dataarea associated with an index must be the same. Run SPRIDEFN to correct the block size specifications.

An attempt to vary an index offline has been rejected because a queue element is currently in use.

A START or PGO command with only a cuu operand has been rejected because the target device does not have any intervention pending.

An internal error was detected while attempting to access SPRI's programming interface. Contact Software Pursuits for assistance.

SPRI detected an invalid SYSxxx assignment while editing a RPT statement. Correct the RPT statement and rerun the job.

SPRI detected a syntax error in the RPT statement while editing a RPT statement. Correct the RPT statement and rerun the job.

When OPTION=LMSG has been specified, this message is issued to indicate that a report is about to be printed or punched. The message is output just before the first report line is output and before any buffer loads or report separators are processed.

Output when OPT=LMSG is specified for a region. The message indicates that a region is reading a job. Job name reflects the reader element name, which may be from a JECL JOB statement and may be different from the VSE job name. The FROM value indicates the origin of the job.

The named reader, RJE station or on-line user just submitted a job or reader data set. This message is only output if OPT=LMSG is specified for the reader.

The indicated queue element is being accessed via the SPRISUB interface and OPT=LMSG was specified on the SELECT statement.

The indicated job has finished executing on the CPU indicated by loc. This message is triggered by the presence of a NOTIFY= operand on a $SPL$RDR control statement or NTFY= on a JECL JOB statement.

A damaged queue condition has been encountered in a DATAAREA data set. SPRI attempts to continue processing by truncating the element on read back. Part of the element will be lost. An ABEND may occur if damage is to the DATAAREA disk usage control blocks. SPRI may continue normal operations. If SPRI does not ABEND then a backup and restore of the indices should be scheduled.

This message indicates that a print or punch report has completed processing for the indicated job. The message is a result of the 'NTFY=' operand on a JECL JOB statement or the 'NOTIFY=' operand on a //RPT or $SPL$OPN statement being used.

This message is the result of a PLOAD that could not find the indicated phase in the SVA. Processing is not altered.

This message is the result of a PLOAD command that specified a phase name. The function is not licensed or was not defined during initial SPRI activation. If the feature is for your reader exit, that name MUST be one of those specified in SPRIDEFN. A reader exit work area size cannot be increased. You must deactivate and then re-activate SPRI to use the feature.

An invalid phase name was specified on a PLOAD command or during a SPRI exit routine load. The requested load of the phase is ignored. The phase name specified may only be for the SPRI reader or page separator exit routines or the EXPRESS distribution table. Check to be sure the phase name is specified correctly and is accessible from the SPRI region.

While loading a SPRI phase SPRI encountered a phase that was not at the correct release level. It is extremely dangerous to attempt to run with phases from different release levels, therefore SPRI is forced to abend. Ensure that SPRI was properly installed, and that no old SPRI phases were left in other libraries.

No queue elements met the selection criteria specified. Make sure that a misspelled keyword was not interpreted as a positional job name.

This message is generated in response to a command that changes or alters queue elements. It lists all the jobs that were affected by the command.

"loc" is running a program using the SPRISUB or SAGEREAD interface and the program is using the NOTIFY option to request full access to all SPRI queues. Normally a program is restricted by normal authorization access. A reply of "Y" will allow the program to access any reports the program desires. Once a "Y" is entered, the question will not be asked again for the current program. A reply of "N" restricts the program to normal authorization.

An invalid JECL statement was detected. Reenter the correct JCL statement or enter a null reply to ignore this JECL statement.

This is a request that the user enters any continuation of the JECL already entered. Enter information as required for your processing.

An unrecoverable I/O error has occurred on one of the data sets required by SPRI. No further recovery is possible and SPRI will cancel due to an I/O error. If this message persists after changing disk drives and re-activating SPRI, the spool queues may be permanently damaged and may require recreation.

A program running in Rx has issued invalid CCWs to a printer, reader or punch being processed by SPRI. If the program was using a real device, an I/O error cancellation would occur due to invalid command codes. The address of the CCB and CCW creating the error are displayed. This error may be caused by illegal carriage control characters or by assigning a non-printer device DTF to a printer (that is, treating a printer as if it were a tape or disk drive).

A report has been created with an FCB= specification that defined the location of channel positions for the report. While the report was being created the user attempted to skip to a channel position that was not defined in the FCB. The line is still spooled normally, however if the report is actually printed with the FCB that was specified when the report was created, a carriage runaway condition will occur. Either the report or the FCB buffer must be corrected to eliminate this error.

An attempt has been made to split a queue element that is referenced by more than one index. This is not allowed and the SPLIT command is ignored.

The PLOAD command was issued using the 'SUBTASK=' operand. The indicated SPRI subtask is already active. The command is ignored. Refer to the 'PLOAD' command in the SPRI documentation for additional information.

The PLOAD command has been issued using the 'SUBTASK=' operand. The internal SPRI subtask cannot be activated because support for the subtask is not included in the SPRI system. The command is ignored. Refer to the 'PLOAD' command in the SPRI documentation for additional information.

A partition or region has completed processing a reader queue job stream. This message is issued when EOJMSG=YES was specified on the JECL JOB statement.

SPRI was unable to determine the correct restart page after an error on a 3800-3 type printer. The may have to manually reposition the printer.

A DEACT command has been accepted by SPRI and the shutdown of operations has begun.

SPRI has signaled the operating system that it is no longer active. All SPRI functions have terminated.

A SPRI DEACT command has been rejected because:

• ports are still being created or
• Unit record devices or RJE lines are still active.

This message names all locations that are still active and which must complete their operations before a DEACT command will be allowed.

The command entered cannot be handled at this time due to some temporary condition. The command should be re-entered in a few moments to see if the condition has cleared. If the condition does not clear, a device is in an improper state for the command to function.

A user exit has been deactivated. The type of exit terminated is indicated by TYPE=. The name of the exit phase is displayed by PHASE=. The user exit routine will not be used again until the next time SPRI is activated or the PLOAD command is used to reload or activate the exit. Use PLOAD RDREXIT=phasename to reload a reader exit. If this message is not preceded by any other messages then either the exit program checked or requested deactivation. Use the Attention Routine (AR) DUMP command to dump the SPRI region so that you might be able to find your error in your exit routine. The constant '***PCSAVE***', located about +X'2500' into the SPRI region/partition, will be followed by the program check address, a PSW that you should ignore, and registers 0 through 15 at the time of the program check.

The report separator routine that would normally be active has been deactivated. The routine will not be used again until the next time SPRI is activated or the PLOAD command is used with the 'RDREXIT=' operand. If this message was not preceded by other messages, the Report Separator routine program checked or requested deactivation. Use the AR DUMP command to dump the SPRI region so that you might locate your error in your report separator routine. The constant '***PCSAVE***', located about +X'2500' into the SPRI region, will be followed by the program check address, a PSW that you should ignore, and registers 0 through 15 at the time of the program check.

A SPRI user exit routine has made an illegal request of SPRI. The action word used to make SPRI requests was invalid. The reader exit or report separator routine will be deactivated. Review the valid codes permitted by the exit routine.

The control block passed to SPRISUB or SAGEREAD contains invalid flag bits, normally because an old copy has been presented out of logical sequence. This is a user error.

The SPRI EXPRESS has encountered an invalid 'Distribute' statement. Correct the statement in error and rerun the job.

Informational message as a result of a previous EXPRESS trace command.

Informational message as a result of a previous EXPRESS trace command.

Informational message as a result of a previous EXPRESS trace command.

This is an informational message as a result of a previous EXPRESS trace command.

This is an informational message as a result of a previous EXPRESS trace command.

This is an informational message as a result of a previous EXPRESS trace command.

4xx Messages  

The reader or region indicated has just read a JOB statement that contains invalid operands or operand values. The reader element is placed in the reader class specified with the 'ERRCLASS=' operand of the MSTRDEFN control statement for SPRIDEFN.

SPRI is waiting for the device named to signal that it is ready to proceed. This is done by stopping the device, then readying it. The START or PGO command with only a cuu operand can also be used.

A $SPL$DSN statement being read by the named task contains invalid operands or operand values. The Job is cancelled.

A $SPL$DSN or SLI JECL statement requested a reader element or book that was not found. Book names are displayed in the form sublib.Book. Source books must reside in a source library assigned in the SPRI region or in SYSRES. If CANCEL=YES was specified, the Job is cancelled, otherwise the error is ignored.

An attempt has been made to read a $SPL$DSN or SLI JECL statement that is nested too deeply within other reader elements. Reduce the nesting of execution time PROCs or reduce the nesting of $SPL$DSN/SLI statements within other $SPL$DSN/SLI books.

This is an internal librarian error. Contact Software Pursuits for assistance.

SPRI's internal tasks have waited at least one minute for one of SPRI's operating system subtasks.

The specified subtask is being restarted after an abnormal termination.

Informational message indicating that the named location attempted to allocate SPRI managed memory and was unable to do so because the memory pool was exhausted. Processing will continue when some other task releases enough memory to satisfy this request. If this message is issued repetitively you should consider increasing the size of the partition or region in which SPRI is running.

Informational message indicating that the task that was previously waiting for memory has obtained it and has resumed processing.

An internal error has been detected while attempting to release SPRI controlled memory. Contact Software Pursuits for assistance.

The Dynamic Class table has been loaded.

The loading of the Dynamic Class table has failed. See prior messages for reason. Correct the Dynamic Class table and reissue the PLOAD command or use the FORCE option to cause the Dynamic Class table to be loaded with errors.

The Dynamic Class table has been verified. The Dynamic Class table has not been loaded.

As a result of using the PLOAD DYNC,FORCE command a Dynamic Class table containing invalid classes has been loaded and activated. Not all Dynamic Classes are usable.

An attempt was made to display the Dynamic Class table before it has been loaded. Issue the PLOAD DYNC command prior to attempting to display the Dynamic Class table.

This message indicates the beginning of the display of the Dynamic Class table.

While processing a PLOAD command SPRI attempted to load the library member DTR$DYNC.Z from IJSYSRS and the member was not found. Catalog member DTR$DYNC.Z into IJSYSRS prior to issuing PLOAD command.

While processing a PLOAD command SPRI attempted to load the library member DTR$DYNC.Z from IJSYSRS and there was insufficient partition GETVIS for LIBR to operate. Increase partition GETVIS and reissue the command.

While processing a PLOAD command SPRI attempted to load the library member DTR$DYNC.Z from IJSYSRS and received a non zero return code from librarian. Contact Software Pursuits for assistance.

An unauthorized user attempted to issued the PLOAD command. The command is rejected.

While processing the PLOAD command the supervisor uses the phase IJBDCTL that must be loaded into the SVA. Load IJBDCTL into the SVA.

While processing the PLOAD command SPRI received a return code from the DYNCLASS macro that it could not recognize and recover from. Contact Software Pursuits for assistance.

While processing the PLOAD command SPRI received a return code from the DYNCLASS macro that it could not recognize and recover from. Contact Software Pursuits for assistance.

The NPARTS= value on the SYS command must be set to greater than 12 in order to run Dynamic Partitions. Increase the NPARTS= value and re-ipl.

The active class must be included in the new Dynamic Class table when attempting to reload the Dynamic Class table with jobs currently active in the Dynamic Partitions. Include the active class in the Dynamic Class table you are trying to load or wait for the Dynamic Partitions to become idle before reloading the Dynamic Class table.

While attempting to load the Dynamic Class table the supervisor could not determine the end of the table. Ensure DTR$DYNC.Z is coded correctly.

A PVARY DYNC,ENABLE was issued for a Dynamic Class that was already disabled. Processing continues.

While using the PVARY command to enable or disable a Dynamic Class a class was specified that does not exist. Ensure that you specify a Dynamic Class that is defined in the currently active Dynamic Class table.

Attempts were made to issue the PVARY command before the Dynamic Class table was loaded. Issue the PLOAD DYNC command before issuing the PVARY command.

While processing the PVARY command SPRI received a return code from the DYNCLASS macro that it could not recognize and recover from. Contact Software Pursuits for assistance.

The PLOAD DYNC command was issued in an environment that does not support Dynamic Partitions. Dynamic Partitions are supported in VSE/ESA 1.0 and above running in 370 mode or ESA mode.

The command issued contained parameters that could not be used together. Consult the command reference and enter the command with the proper parameters specified.

While editing the Dynamic Class table an invalid spool device was detected. You may:

1. Correct DTR$DYNC.Z and reissue the PLOAD DYNC command, or
2. Issue the PLOAD DYNC,FORCE command to cause the Dynamic Class table to be loaded even though it contains invalid classes.

SPRI received a return code that it could not recognize and recover from while attempting to ALLOCATE a Dynamic Partition that had terminated. Contact Software Pursuits for assistance.

The PLOAD DYNC,ID= parameter was specified incorrectly. ID= must be a single alphanumeric character. If this parameter is specified on a VSE/ESA 1.2 or earlier system it is ignored.

SPRI received a return code from the DYNCLASS macro that it could not recognize and recover from while processing the PVARY command. Contact Software Pursuits for assistance.

A PVARY DYNC,DISABLE was issued for a Dynamic Class that was already disabled. Processing continues.

A PVARY DYNC,ENABLE command was issued for a Dynamic Class that contains errors in its class definition. A Dynamic Class that has an invalid class definition can not be enabled. To use this class, correct the definition statements in DTR$DYNC.Z and reissue the PLOAD command.

5xx Messages  

This message is issued by the DISPLAY command to show which reports are actively being created on the system. The operands displayed match those defined for RPT JCL statements. SEQ= is the unique report Sequence Number assigned to the report or reader element in the spool system. The page and line numbers shown indicate the current status of each report. Additional information related to each report can be obtained with a QUEUE SEQ=... Command.

This message is issued in response to a DISPLAY PRT, PUN or ACTIVE command. Its purpose is to describe the status of printers and/or punches. A device listed as **FREE** will not select any reports until a START or SELECT command is entered. **DOWN** indicates that a DOWN command has been issued for the device and that an UP command is required before the device can be used. A device listed as **IDLE** is currently not processing a queue element. Selection criteria is available and the device will begin printing or punching when a report enters the spool system that matches the selection criteria. For devices that are busy, information identifying the report and its current position is displayed. PLEFT and LLEFT indicate the pages and lines remaining in the current copy of the report. All selection information and options active for a device are always displayed. More information about specific reports can be obtained with a QUEUE SEQ=... command.

This message is issued in response to the DISPLAY ROUTE command. The display shows each group, location and alias code and its full expanded definition as used by SPRI. Any imbedded groups or implied references or definitions are detailed and listed.

This message is issued in response to the DISPLAY RDR command. Its purpose is to show the status of real readers. Real readers will indicate the status of the reader element being created. RJE readers are not displayed.

This message, which is issued in response to a DISPLAY DISK command, indicates the amount of disk space in use. If a data set is close to 100% full, more space should be added to the data set at some convenient time. If the data set is always less than 70% full, perhaps too much space has been allocated and it is being wasted. The 'HIGH' column indicates the high water mark: the most amount of space used since the data set was last created.

This message is issued in response to a DISPLAY command to list the options specified in the SPRI definition file via the SPRIDEFN program. The lines listed are in the same format as the control statements originally used as input to SPRIDEFN. See 'SPRIDEFN' for a description of the control statements and options.

This message lists the amount of output ready to be processed for each printer and punch form. The message is issued in response to the DISPLAY FORMS command. Only output that would be selected by the CPU or RJE station under normal conditions will be shown. Multiple copies and multiple routings are considered as well as pages or lines already processed. If a report has a group Routing Code it will be displayed on each CPU or RJE station that is a member of that group, although it will only be processed at one location. This display cannot consider the activity or future activity of another CPU or RJE station.

This message is issued in response to a DISPLAY JOBS command. A count of the number of Jobs ready to run in each class is displayed. The Jobs considered are those with routing to the current CPU or to the Group Name to which the CPU belongs. Jobs that have begun execution are not included in the count.

This message lists the number of cards and lines ready to be processed for each printer or punch form. The message is issued in response to the DISPLAY LINES command. Only output that would be selected by the CPU or RJE station under normal conditions will be shown. Multiple copies and multiple routings are considered as well as lines already processed. If a report has a group Routing Code it will be displayed on each CPU or RJE station that is a member of that group, although it will only be processed at one location. This display cannot consider the activity or future activity of another CPU or RJE station.

The detail lines associated with this message indicate the current status and options for the processing regions and information on reader elements being read by the partitions or regions.

The detail lines indicate the status of each RJE line and the status of any terminal logged onto a line.

This message is the heading message for the display of SPRISUB or XPCC requests.

Title message for the DISPLAY AUTHDEVICE command.

Title message for the DISPLAY AUTHQUEUE command.

Title message for the DISPLAY STATUS or PDISPLAY T command. The status of various resources are displayed.

This is a header line indicating which type of NJE status information is to follow.

This message is in reply to a QUEUE command. It lists information pertaining to reader queue elements. See the queue command for details on this display.

This message is in reply to a QUEUE command. It lists information pertaining to punch queue elements. See the queue command for details on this display.

This message is in reply to a QUEUE command. It lists information pertaining to printer queue elements. See the queue command for details on this display.

This is a header line indicating which type of APPC status information is to follow.

The APPC feature has not been 'CONNECTED' by issuing a CONNECT APPC command. Nothing else can be displayed unitl the APPC is active.

No APPC node entries were successfully initialized when the APPC feature was activated. APPC nodes will not be able to connect to SPRI. No valid definitions have been found.

No TPN table entries were successfully initalized when the APPC feature was activated. Nodes can connect but no APPC TP's will be allocated. No queue element transfers or message traffic is possible. No valid definitions were found.

In response to 'D APPC,N=nnnnnnnn' when node nnnnnnnn is not initialized. Either an incorrect node name was entered or the definition was not found during initialization. A node can be dyanmically added to SPRI by defining the node in SPRIDEFN and issuing a PLOAD APPC,N=nnnnnnnn command.

In response to 'D APPC,TPN=nnnnnnnn' when TPN nnnnnnnn is not initialized. Either an incorrect TPName was entered or the definition was not found during initialization. A TPN can be dyanmically added to SPRI by defining the TPN in SPRIDEFN and issuing a PLOAD APPC,TPN=nnnnnnnn command.

A 'D APPC,N=nodename' was issued for APPC node name defined for the SPRI system on which it was entered.

6xx Messages  

An attempt has been made to use the SPRISUB subprogram, but use of the routine is not possible if SPRI is not active. The Job is cancelled.

A required control statement for a SPRI utility has been omitted or contains invalid operands or operand values. Review the control statements permitted by the SPRI utility you are using. The Job is cancelled.

While using the SPRIUSER utility, the user routine made several invalid requests. The maximum number of error returns to the routine have been made and the Job is now cancelled. This is a user error in passing requests to SPRIUSER.

7xx Messages  

The line indicated could not be opened. Check for problems with the line and retry the command.

While making a request of BTAM for the device 'loc' on line 'cuu', an error was detected by BTAM. The error code set by BTAM to identify the error is 'cc'.

After an I/O request using BTAM completed, BTAM indicated that an error had occurred by posting the completion code 'cc'. The terminal affected is 'loc', line 'cuu'. This is generally a hardware error.

While deblocking input from an RJE terminal on line 'cuu' for terminal 'loc', an error was detected in the format of the block received. This may have been caused by a transmission error or by pressing the wrong button at the RJE station. The reader is drained by flushing all card input until end-of-file.

An attempt was made to logon a terminal that was not defined to SPRI. Submit a RJETERM statement to SPRIDEFN to define the terminal. The definition is immediately available without bringing SPRI down.

The line indicated was successfully opened by the LOPEN command.

The line indicated was successfully closed by a LCLOSE command or the line may have been forced closed due to some error on the line or terminal. The line may be re-opened with the LOPEN command if desired.

An Intervention Required status has been raised by the terminal and line indicated. Normal processing should resume when this error is corrected at the terminal site.

The first card read from an RJE station must be a LOGON card. The reader will be flushed until end-of-file. Submit a valid LOGON statement after the reader has been run out.

The password required to logon the RJE terminal is missing or invalid.

Terminal "loc" has been logged of the system. It was attached to line "xxx". The time of day the logoff occurred is also displayed. The logoff may be the result of a LOGOFF command from the terminal, a LOGON command from the terminal, or due to some error condition.

A valid LOGON statement was processed for terminal "loc" on line "xxx". The terminal may now proceed with normal RJE functions.

While processing a Line Open Command (LOPEN), the line indicated by 'CUU=cuu' has been found to be currently assigned to another region and is assumed to be unavailable. The line indicated is not opened and open processing for any other lines requested continues.

This message is issued when a BTAM controlled line (CUU) for a BTAM RJE task has been requested to be opened. The open was initiated by a LOPEN command entered at a console. The BTAM RJE line for the CUU specified is already in an open state.

This message will always follow message SPRI703I. It formats selected fields from the DECB to provide additional information pertaining to an error that has occurred. The DECB labels and decimal displacements are shown below; for detailed information on their meanings consult the section on 'DECB Fields' in a BTAM manual (IBM publication GC27-6989 or its equivalent).

IDLABEL	DISPLACEMENT
CC	IJLDEECB / +0
OP	IJLDEOF1 / +4
RI	IJLDEORI / +8
SNS	IJLDESNO / +16
LCC	IJLDELCC / +20
OF2	IJLDEOF2 / +24
TPC	IJLDETPC / +28

This message is provided each time a terminal logs off SPRI to indicate transmission counts.

An action has been requested to an RJE terminal that is not logged on.

The remote station is already logged on. The new logon attempt is rejected.

An action has been requested for an RJE line that is not open.

SPRI was unable to perform the auto-logon function. The line must use a LOGON command from the RJE station since the automatic logon function has been suspended.

An attempt was made to use the RJE. SPRI has determined that the required support is not currently available. Check the following:

1. Run SPIEXPIR, without any control cards, and check the line that indicates if RJE support is/is not available on your system. If the support is not available, contact SPI Technical Support.
2. Check the SPRIDEFN file to be sure you have RJELINE entries (and any associated RJETERM) for the line(s) you are attempting to use. If there is no RJELINE entry, add the proper entry and process the SPRIDEFN file. Please note that SPRI must be recycled for the new RJELINE entries to take affect.

Contact Software Pursuits for Technical Support or your sales representative for additional information on the use of RJE.

An exception response was received from an SNA/RJE workstation during element transmission. Transmission of the current element is terminated; the element is returned to its original status. xxxxxxxx defines the SNA/RJE workstation. yyyyyy is the VTAM request that was in progress when the negative response was received. The negative response is defined by nnnn.

This may be a temporary or permanent error. If the same failure occurs during retransmission contact your VTAM systems programmer or SPI Technical Support for an explanation of the VTAM sense information received. This may be a workstation or VTAM parameter definition error.

An internal error has been detected during SNA/RJE processing. The SNA/RJE function is terminated. Please dump the SPRI region as soon as possible and contact SPI Technical Support.

Session has successfully logged onto SNA/RJE from workstation yyyyyyyy.

Session has successfully logged from off workstation yyyyyyyy.

All sessions from workstation xxxxxxxx have been closed and the workstation has been logged off the system.

A command was issued which is invalid for an SNA/RJE workstation.

The attempt by the indicated LU to logon from workstation yyyyyyyy failed. The reason is defined by the return code field, RC=nnnn. The content of the RC field is explained in VTAM documentation. This is usually a VTAM definition error.

A command was issued for workstation xxxxxxxx. The workstation is not logged on. The command is ignored.

A SNA/RJE command was issued while SNA/RJE is being stopped. The command is discarded. Wait until message SPRI293I is displayed to restart the RJE function.

The element defined by Job job, sequence number nnnnn is compacted. The workstation session definitions do not specify compaction. Correct the VTAM definition(s), logoff and logon the workstation and retry the transmission of the element.

The request to start the first session on workstation xxxxxxxx failed. A SPRI message (SPRI737, and SPRI746-SPRI748) will follow this message to define the reason for the failure. This will usually be a SPRI definition problem. Correct the SPRI definition(s) and reissue the workstation logon request.

The request to start session session on workstation yyyyyyyy failed. A SPRI message (SPRI734-SPRI739) will follow this message to define the reason for the failure. This will usually be a SPRI definition problem. Correct the SPRI definition(s), log the workstation off and reissue the logon request(s).

A request to start a session on workstation xxxxxxxx failed due to exceeding the SESSIONS parameter. This message follows message SPRI733W.

The password specified in a session logon request is incorrect. This message follows SPRI733W.

A request to start a session was rejected because the workstation is being logged off. Resubmit the logon request when workstation logoff is complete. This message follows SPRI733W.

A request to logon a workstation failed because the maximum number of workstations are already logged on. The maximum number parameter is specified in the CPU definition SNARJE parameter. Correct the CPU definition entry and restart the SNA/RJE function for the change to take effect. This message follows SPRI732W.

A RJELINE definition specified a cuu that is not present in the VSE Pub table.

A logon request was received from a session that is not valid for the workstation displayed in the preceding SPRI733W message. Verify that the logical unit attempting to logon is valid for the indicated workstation. Correct the RJETERM definition and restart the workstation affected if required.

Workstation xxxxxxxx has been logged by logical unit yyyyyyyy.

This message is issued when SPRI fails in an attempt to allocate storage, in the SPRI region, for an RJE workstation during LOGON and must abort the logon of the VTAM RJE station. Other messages will accompany this message indicating the name of the logical unit the RJE workstation is known as to the SPRI subsystem.

This message is issued when SPRI fails in an attempt to allocate printer task control blocks for the RJE station, not enough were defined, for an RJE workstation to LOGON. SPRI must abort the logon of the VTAM RJE station. Other messages will accompany this message indicating the name of the logical unit the RJE workstation is known as to the SPRI subsystem.

SNA/RJE initialization has been terminated due to error defined by preceding message.

The SNA/RJE function has been successfully initialized. Workstations can begin their logon process.

A PSTART RJE,SNA command was issued while the function was already active or initialization was in flight. The command is ignored.

Incorrect CPUID parameter specified in a workstation's RJETERM definition. The workstation is identified in the preceding SPRI732W message. Correct the RJETERM definition and restart the workstation.

Incorrect terminal type parameter specified in a workstation's RJETERM definition. The terminal type for SNA/RJE must be LUT1. The workstation is identified in the preceding SPRI732W message. Correct the RJETERM definition and restart the workstation.

The workstation identified in the preceding SPRI732W message is not defined in the SPRI definitions. Correct the workstation's logon workstation ID or update the SPRI definitions.

If output during SPRI activation, the named device cannot be used for input or output operations since no SYS number was available to assign to the device. The device is placed in a Down status and activation continues. While attempting to process an RDEFAULT statement specifying tape spooling, a SYS number could not be found for use in the SPRI region. The RDEFAULT statement is rejected. It can be re-entered when less tape spooling is active, or more LUBS should be assigned to the SPRI region.

A tape spooling request was made but the cuu or mode specification is in error. You will be prompted to re-enter a valid cuu and mode value.

A job is requesting tape processing, but a cuu was not specified. Enter the device address and optionally the mode, or enter CANCEL to cancel the request for tape spooling or the BACKUP, JOBACCT or RESTORE command.

A report lineup request was made from the Report Separator exit routine or with OPTION=LINEUP. The printer should be checked for proper alignment of the form. The test pattern may be repeated each time the printer is stopped, then started or it may start the actual report when the printer is readied. The actual text of the report is always started if a RESTART command is entered.

A CANCEL command specified the tape operation described in this message. If spooling to tape, spooling to disk is now performed instead. If the tape was being used by the BACKUP, JOBACCT or RESTORE commands, the command is immediately terminated.

This message is issued to inform the user that the name job, submitted from location 'loc' has begun writing to the named tape. The user may be spooling directly to tape or the tape may be the output from a JOBACCT or BACKUP command. If the RESTORE command is used, this message indicates the tape being read and the message text says 'READING'.

A tape operation has completed for the named tape drive. 'loc' and the job name indicate the origin of the command creating the tape. The tape may have been written when spooling direct to tape or through the use of the JOBACCT or BACKUP commands. The tape was being read if the RESTORE command was used.

A tape operation has been requested for the named drive. The tape mode (mm) may also have been specified for output tapes. "loc" and the job name indicate the origin of the command creating the tape. The tape may have been requested when spooling direct to tape or through the use of the JOBACCT, BACKUP or RESTORE commands. If the named tape drive should be used, simply press enter. If you enter "CANCEL", the tape command is immediately terminated or the request to spool to tape is denied and spooling to disk is performed instead. Entering a new "cuu,mm" value changes the location and recording mode of the tape. If the mode is omitted, the default mode for the tape drive is used.

The tape drive requested is not available because it does not exist, is in a down status, is assigned in another region, or because it is in use by another SPRI command or user task. You will be asked to enter a new tape drive specification.

A BACKUP or RESTORE command has been entered and selection criteria may now be specified. Enter a SELECT statement in the same format as used by SPRICPYV for the BACKUP command, and in the same format as for SPRIPRNT when the RESTORE command is used. After each command is processed you will be asked for additional SELECT commands. If no SELECT command is entered, no further elements are selected. Note that the RESTORE command enters all selection criteria before starting to search the input tape, while the BACKUP command writes tape each time a SELECT statement is entered.

This message is issued to allow continuation of BACKUP command lines. Enter any additional continuation lines. A null entry indicates the end of input. Be sure that you reply to the outstanding read and not to AR. The entry of certain BACKUP 'SELECT' statements may cause an additional BACKUP job to start.

The tape being used to restore from contains a block that is larger than the blocksize specified. If the BLKSIZE= parameter was not specified on the RESTORE command the default value in the Master Definition file is used. Rerun the RESTORE command with a larger BLKSIZE= value.

The tape being used to restore from can not be recognized as a valid SPRI data tape. If you are attempting to restore data from a tape that was produced by VSE/POWER use the SPRIPRNT utility instead of the RESTORE command. Rerun the RESTORE command with the correct input tape.

The output file could not be opened. Verify that the file name and label information is correct and reenter the command.

Informational message indicating the named file has been opened and is being processed.

Informational message indicating that the processing of the named file is complete and the file has been closed.

An end of volume condition has been detected while processing an unlabeled tape. Reply with the CUU of the next tape to use, or EOF to stop processing at this time.

8xx Messages  

An invalid device type was specified with the UCS or LFCB commands.

A DOWN command had been issued to this device previously. No commands will be accepted until an UP command is entered for the device.

The device specified in an UP command is already in an UP status and the command is not needed.

The device specified in a DOWN command was already in the DOWN status and the command is not needed.

The UP command just entered has been processed and the device has been placed in the UP stat