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.
This publication applies to various Software Pursuits, Inc program products.
All messages, unless otherwise specified, are in the format:
- Indicates a Software Pursuits, Inc message. nnn
- The assigned number for a give message. t
- Indicates the type of message being issued.
- 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.
- A cancellation message. A severe error has occurred that caused processing to be canceled.
- A decision is required. Some type of decision is required that will require a response to the message.
- An informational message. Action is not generally required.
- A severe error message. Some type of action is required to complete the processing.
- A warning message. A moderately severe error has occurred that may or may not require action. message The message text.
This message informs the operator how many days remain before your Software Pursuits products expire and will no longer function. This message will only appear if 20 or fewer days remain. If the message suffix is a D, a console response of end-of-block is required in order to insure that the operator sees the message. If 10 or fewer days remain, both message formats require a reply.SPI101A System expiration exceeded.
If you have not received your expiration update, contact Software Pursuits immediately by phone. If you have received the update it should be applied as soon as possible. When the expiration date is reached message SPI101A is issued.
This message appears when your Software Pursuits products have expired. You should contact Software Pursuits by phone immediately. If you use MVT/VSE, it will now be necessary to execute the SPIEXPIR program before the first JOB statement is processed.SPI102W CPU cpuid not licensed for product
CAUTION: Any attempt to disable or defeat the expiration mechanism may cause SPI programs to malfunction, perhaps on a delayed basis. Systems may appear to run, then cease functioning completely without notice.
Back dating a system will be detected and products will disabled with message SPI118C.
The indicated Software Pursuits product is not licensed for the indicated CPU. Use of the product is allowed for a maximum of 25 days for the purpose of utilizing a backup side or testing.SPI103W nn days of unlicensed usage remain.
This message is accompanied by message SPI103W or SPI103D which report the number of unlicensed usage's to date. If you must run on an unlicensed CPU for an extended period of time, you should contact Software Pursuits to make arrangements to license the CPU in question.
A Software Pursuits product has been brought up on a CPU for which it is not licensed. nn represents the number of days left on which the product will still activate, provided the expiration date is not reached first. This message is preceded by message SPI102W which displays the CPU serial number and product in question. If the message suffix is a D, a console response (just press enter) is required to ensure the operator sees the message. Contact Software Pursuits immediately by phone if you need to continue running on this CPU.SPI104C Excessive unlicensed usage.
An attempt has been made to run a Software Pursuits product on a CPU for which it is not licensed for more than the permissible period of 25 days. This message is preceded by message SPI102W which displays the CPU serial number and product in question.SPI105C CPU serial number table full.
Contact Software Pursuits immediately by phone for assistance.
An attempt has been made to run a Software Pursuits product on a CPU for which it is not licensed and there is insufficient space in the CPU serial number table to hold another unlicensed CPU. Contact Software Pursuits immediately by phone for assistance.SPI106C Unable to PFIX
Program SPIEXPIR requires at least 16K of real memory to PFIX. Increase your ALLOCR memory for the region where SPIEXPIR will run. MVT/VSE systems need to increase the amount specified in a DEFINE MAXREAL= statement. An alternate solution is to add the "REAL" operand to the EXEC statement.SPI107C Too many CPU's-Contact Software Pursuits.
Program SPIEXPIR encountered a situation where there was no room in the CPU serial number table to add licensing information for all of the indicated CPU's. One possible cause of this condition is attempting to add new CPU's after running on unlicensed CPU's. Contact Software Pursuits for assistance.SPI108W VM Class C or E is required
In order for the license management facility to obtain the correct CPU serial number on older versions of VM (before VM/ESA 1.2), your batch machine must have class C or E privileges. Processing may continue. The system will treat your CPU as unlicensed.SPI109C Update not for this customer.
The UPDATE control statement submitted to SPIEXPIR is valid but is for a different customer. If you have copied a system from another user, is necessary to run with a NEWCUST control statement and a valid OVERRIDE control statement. Contact Software Pursuits to get today's OVERRIDE password as well as instructions on how to set your customer name and number.SPI110C Custom phase not found.
The phase containing your customized expiration and licensing information could not be found in the system core image library. All $$B prefix phases must be contained in SYSRES, except for VSE/SP systems. With VSE/SP, the phases must be accessible from all partitions and duplicates of the phases must not be present.SPI111C GETVCE failure for SYSRES.
A component of your expiration update control system received a bad return code from a GETVCE macro for SYSRES. The job is cancelled. This error indicates that your SYSRES cannot be accessed properly. A re-IPL of your operating system should correct this problem.SPI112C OVERRIDE error
An error in the OVERRIDE statement was encountered. This is usually due to the word OVERRIDE being spelled incorrectly. Check for entry errors and correct them.SPI113C OVERRIDE password invalid-Contact Software Pursuits.
The OVERRIDE password on the OVERRIDE control statement submitted to SPIEXPIR is invalid. Check the OVERRIDE statement for mis-keyed characters.SPI114C Custom phase invalid-Contact Software Pursuits.
After ensuring the statement was correctly keyed, contact Software Pursuits for assistance. Note that a given OVERRIDE password is valid for only one day and for only one use on that day.
The phase containing your customized expiration information was found to contain invalid information by program SPIEXPIR. The most likely causes of this problem areSPI115I Expire updated from weekday, dd month yyyy
that either the phase was damaged or the system core image library has been damaged. Attempts to defeat the expiration update system by altering the custom phase can also
lead to this message. You will need to restore all $$BSPI prefix phases or you can re-install the common support products library and apply a new expiration update.
This message is issued by SPIEXPIR at the end of a successful run when an update has been applied. The date mentioned is the expiration date of your Software Pursuits products before SPIEXPIR was run. Another message is issued to indicate the new expiration date.SPI116I CPU cpuid now licensed for product
This message is issued by SPIEXPIR at the end of a successful run. It indicates the indicated CPU is now licensed for the Software Pursuits product.SPI117C Insufficient GETVIS.
The expiration control system was unable to obtain a area of 2K from the region GETVIS during startup of a Software Pursuits product. Rerun the startup job with a larger GETVIS area. Use:SPI118C Too many uses on this date-Contact Software Pursuits
- For VSE: The SIZE= operand on the EXEC statement.
- For MVT: The GETVIS= operand on the EXEC statement.
The expiration control system detected excessive activation of Software Pursuits products on the current date. The date must be set ahead to the next day to permit more usage. If this is not possible, contact Software Pursuits. It will be necessary to perform an expiration update before any Software Pursuits products will function.SPI119W This CPU is cpuid and it is not licensed for any SPI product
The expiration control system detected that the CPU indicated is not licensed to run any product from Software Pursuits. This is usually caused because the wrong CPU serial number was reported to Software Pursuits to produce an expiration update. Call Software Pursuits with the text of this message.SPI120C Phase SPILBSVA not in SVA
The expiration control system requires the phase SPILBSVA to be in the SVA in order to execute. Use the SET SDL command in BG to load this phase into the SVA, then re-run the job.SPI121C SPILBSVA R/C = rc FDBK = yy, FOR FUNC = zz
The system has encountered an error in SPILBSVA.SPI122C SPIEXPIR type request failed
If you should receive a Return Code of 54 with a Function Code of 14,check to be sure you have enough space/directories in the library being used.
For any other error, please contact Software Pursuits Technical Support.
The SPIEXPIR program requires more space than allocated.SPI123I Cust=nnnnnn customer-name
If type is GETVIS, use:
- For VSE: The SIZE= operand on the EXEC statement.
- For MVT: The GETVIS= operand on the EXEC statement.
If type is PFIX, use a
- For VSE/ESA 1.3 or later: // SET PFIX LIMIT=nnnK
- All other systems: ALLOC R,BG=nnnK
statement to resolve the situation.
This informational message indicates the customer number and name as known by the expire system.SPI124C CDLOAD failure for SPIMMGT. RC=cc
An attempt was made to load the SPIMMGT program, but the attempt failed. The RC= operand indicates the return code from the CDLOAD macro. Either the program could not be found, or insufficient GETVIS space was available to load the program. The SPIMMGT may reside in the SVA, eliminating the need to GETVIS space.SPI125C CDLOAD failure for SPIDYLNK. RC=cc
An attempt was made to load the SPIDYLNK program, but the attempt failed. The RC= operand indicates the return code from the CDLOAD macro. Either the program could not be found, or insufficient GETVIS space was available to load the program. The SPIDYLNK may reside in the SVA, eliminating the need to GETVIS space.SPI127C $IJBAR Scan error location=xxxxxxxx
The SPI Common Interface is not active, as required by this program. Load the necessary SPI Common Interface programs into the SVA, execute SPIIFACT to activate the interface, then retry executing the failed program.
The SPI Common Interface could not find the hook point for the AR exit named by "location=xxxxxxxx". This is probably a vendor compatibility problem. Contact Software Pursuits Technical Support.SPI128I JCLEXIT=RELOAD not valid on this system
This common is only valid on VSE/ESA release 1.2 systems and higher. It does not apply to MVT/VSE or systems below VSE/ESA 1.2.SPI129I SPI JCLEXIT is [ON | OFF]
This informational message indicates if the SPI JOB control exit is on or off. This message should always indicate that the JCLEXIT is on, unless there is a problem or SPI technical support has directed you to turn it off. When the JCLEXIT is off, many SPI products will not function properly or may run in a degraded mode.SPI130ISPI Common Interface Status:
This informational message is output at the beginning of the SPI AR STATUS command. If is followed by the actual status display.SPI131I SPI Release: n.n.nnn
This message output by the SPI STATUS AR command indicates the release level of the SPI common component. nnn indicates the highest APAR applied to the SPI component.SPI132I Operating system is type Release n.n.n
This message displays the type of operating system (VSE or MVT/VSE) being used and the release level of the system as determined by the SUBSID macro.SPI133W SPI JCLEXIT already active
The SPI JCLEXIT=RELOAD command has been entered and it has been determined that the SPI JCLEXIT has already been loaded/reloaded. The SPI JCLEXIT=RELOAD command was designed only to re-establish our JCLEXIT after a new $JOBEXIT or $JOBEXnn has been reloaded into the SVA. For more information on the SPI JCLEXIT command please see SPI publication SP01-0001 Support Products User's Guide.SPI134I R.IFDCT=X'raddr' V.IFDCT=X'vaddr'
This message indicates the virtual and real addresses for SPIIFDCT.SPI135I SPI installed at level n.n.nnn
This message displays the release and APAR level of the SPI Common Interface component when it was initially installed at the user site.SPI136I SPI APAR n.n.nnn is applied
This message indicates the APAR shown in installed and applied on the current system.SPI137I APAR bit map is not valid
This message is produced when the SPI APARS command determines that the APAR bit map is not valid. Contact SPI Technical Support.SPI138I Operating mode is: mode
Indicates the operating mode of the system. One of the following will be indicated:SPI139I Request complete
This message indicates that the requested SPI AR command has completed.SPI140I help-display
This message is output from the SPI HELP/? command and displays the various valid SPI commands.SPI141W JCLEXIT DISABLE will affect the operation of SPI products
This message is produced whenever the VSE/ESA release 1.2 (or later) JCLEXIT DISABLE command is processed. The purpose of this message is to inform the user that by disabling the VSE job control exit they may cause SPI products to fail or run in a degraded mode. For more information please see SPI publication SP01-0001 Support Products User's Guide.SPI142ISPI JCL EXIT is present
This message is output when JCLEXIT SPI is entered in the BG partition or any MVT/VSE region and the SPI JOBEXIT sees it. If the SPI JOBEXIT is not present, then job control will kick it out as an invalid statement.SPI143C SPIIFSVA common interface needs to be at level n.n
Some SPI product has issued a request to the SPI common component that is not available in the release of the SPI common component running at your data center. The release level indicated is the minimum level the you must be running to get the required support. Contact SPI Technical Support to receive a new product tape with the proper release.SPI144C RC=rc from programname
An unexpected return code was returned by an internal call to the named component. Contact Software Pursuits for additional assistance.SPI145C Invalid hex digit encountered
The operand requires the use of hexadecimal digits. Each character must be a numeric digit of zero through 9, or one the letters A through F.SPI146C Digits are transposed or incorrect
One of the digits is missing, incorrect, or in the wrong position. An internal check digit calculation was performed to verify that your value was correctly keyed. This check failed. Please recheck the value to be entered.SPI147C Customer is not numeric
The customer number must be specified as a numeric value.SPI148C Invalid statement or statement out of sequence
The statement was not recognized or is out of context. Recheck the order of your control statements.SPI149C Expire applied out of date sequence. Override required.
Expiration updates must be entered in the sequence released by Software Pursuits. If you attempt to reapply an expire or apply an old expiration update you will get this message. To verify your current expiration date run the SPIEXPIR program with no control statements.SPI150C Incorrect value detected
An internal error was detected while processing an expiration update. Please contact Software Pursuits for assistance.SPI151I System now expires weekday, dd monthname yyyy
This informational message indicates when your Software Pursuits products will next expire. You can generate this message my running SPIEXPIR without any control statements.SPI152C Statement out of sequence
The SPIEXPIR program issues this message if an UPDATE statement follows CPU statements and the CPU statements are required. Rerun your job placing the UPDATE statement before the CPU statements.
An attempt was made to activate the SPI Common Interface, however the interface was found to be already active. The request is ignored. The message indicates the version and modification level of the interface as well as the real storage address where it resides.SPI201C Subsid failure RC=xxx, NAME=nnnn
The SUBSID macro indicated that a required subsystem is not present. Check to insure that the proper release of the operating system is installed. Contact Software Pursuits if you cannot quickly resolve the problem.SPI202C PHASE phasename not found in SVA
The phase name indicated must be in the SVA before the SPI Common Interface can be activated. The phase name should normally be specified in the $SVA0000 phase. This phase must not be directory resident; the full text of the phase must be loaded into the SVA.SPI203C Unable to PFIX
The SPIIFACT program needs to PFIX a small portion of its code. Use the ALLOCR command under DOS/VSE or the DEFINE command under MVT/VSE to increase the real memory available for page fixing. You may also use the "REAL" operand on the EXEC statement.SPI204C Unable to PFIX in the SVA
The SPI Common Interface requires that certain portions of its code be locked into memory in the SVA. The attempt to allocate real memory for this page fixing failed. The page pool must be increased in size before attempting to activate the SPI Common Interface.SPI205W Unable to locate AAAADR or it is not zero
The activation routine for the SPI Common Interface must locate the label "AAAADR" in the nucleus, but it was unable to do so. This is caused by activation of another program product that is not hiding properly in the real memory pool. This problem does not occur when the SPI Common Interface is activated first. If the problem continues, contact SPI Technical Support.SPI206C GETREAL failed, page pool too small.
The SPI Common Interface requires that certain portions of its code be locked into memory in the SVA. The attempt to allocate real memory for this page fixing failed. The page pool must be increased in size before attempting to activate the SPI Common Interface.SPI207W Cannot save interface address
The SPI Common Interface will be unable to use its SVC intercept routine because it could not locate an appropriate place to save the interface address. Please contact Software Pursuits with the release level of the operating system you are using. The system is fully functional, even when this message is issued.SPI208W Unable to locate type intercept point
The SPI Common Interface will be unable to use an intercept routine because SPIIFACT was unable to locate its patch point within the nucleus. "type" might be:SPI209W Using type PSW swaps
- SVC for supervisor calls,
- PCK for program checks,
- EXT for external interrupts, or
- I/O for I/O interrupts.
The probable cause is that another routine has performed a PSW swap. The Common Interface will be forced to also use PSW swaps to support the named function. Note that SVC support is the only support required by all SPI products. The other functions might never be needed or used. The system is fully functional, even when this message is issued.
The SPI Common Interface will be unable to use an intercept routine. "type" might be:SPI210I SPIIFSVA(v.m) now active at X'address'.
- SVC for supervisor calls,
- PCK for program checks,
- EXT for external interrupts, or
- I/O for I/O interrupts.
The probable cause is that another routine has performed a PSW swap or PSW swaps were requested with UPSI xxxxxx1x when SPIIFACT was executed. The Common Interface will be forced to also use PSW swaps to support the named function.
Note: SVC support is the only support required by all SPI products. The other functions might never be needed or used. A PSW swap might cause problems for other products which attempt to locate routines within the nucleus. Those products experiencing difficulty will issue error messages. Under most circumstances, this message may be ignored.
The SPI Common Interface has just been activated. The message indicates the version and modification level of the interface as well as the real storage address where it resides.SPI211C Program: pgmname cannot run in a dynamic partition
This condition applies to VSE/ESA Release 1.1 and 1.2 systems only. The program you are executing (pgmname), cannot run in a VSE/ESA dynamic partition because it uses facilities that are not supported for dynamic partitions. The program is cancelled and should be re-run in a static partition (BG or F1 through FB).SPI251I SPIZAPCK vv.mm BEGINNING
This is the normal message displayed at the start of the execution of SPIZAPCK. The characters vv.mm are replaced with the version and modification level of SPIZAPCK.SPI252I SPIZAPCK ending
This is the normal message displayed at the end of the execution of SPIZAPCK.SPI253I Processing PHASE=phasename
SPI254A Product=product duplicate byte map phases present, SYSRES used
SPIZAPCK has determined that duplicate phases exist for recording the application of fixes for the named product. The phase in IJSYSRS is used. Inform the Systems Programming staff. Duplicate phases are not necessarily an error condition but may provide confusion and incorrect reporting of applied maintenance. Software Pursuits uses core image library phases to record the fixes that have been applied to the named product. SPIZAPCK has determined that a copy exists in the IJSYSRS core image library and also in a concatenated private core image library. The information in the copy in IJSYSRS is what will be reported in following messages. Systems Programming staff should determine which phase has been used to log the fix information and delete the other phase.SPI255I Product=product Release=vv.mm
This message displays the version and modification level of the named product.SPI256I product installed at level: vv.mm.ptf
This message displays the version, modification, and PTF level at which the named product was shipped from Software Pursuits. This number does not reflect any maintenance done by the customer. It is only changed by PUT/INSTALL tapes provided by Software Pursuits.SPI257I product APAR vv.mm.ptf not logged
This message displays the version, modification, and PTF level of a PTF that has not been applied. You may wish to read the description on the PTF to determine the applicability of the fix to your installation.SPI258I product APAR vv.mm.ptf thru vv.mm.ptf not logged
Please see message SPI257I for an explanation of this message.SPI259I product APAR vv.mm.ptf highest APAR applied
This message displays the version, modification, and PTF level of the highest PTF that has been applied to the product.SPI260I product APAR vv.mm.ptf revoked
This message displays the version, modification, and PTF level of a PTF that has been marked as revoked.SPI261I product APAR vv.mm.ptf invalid state
This message displays the version, modification, and PTF level of a PTF whose byte map entry is invalid. Please contact Software Pursuits technical support for further assistance. This may indicate a misapplied PTF.SPI262A Product=product missing PHASE, bypassed
This message indicates that the phase containing the fix information was not found in the concatenated core image library search chain. This is not an error if the named product is not installed at your installation. Please contact Software Pursuits technical support for further assistance only if the named product is installed at your installation.SPI263I yyy product vv.mm APARS have not been logged below the highest applied
This message displays the number of non-applied PTFs below the highest applied PTF.SPI264A Internal error, contact SPI, RC=rc
An internal error has occurred during the processing of SPIZAPCK. Please contact Software Pursuits technical support for assistance. Return codes are:SPI265I Parm value=value specified
- 04 Phase Table run out
- 08 Byte map does not contain internal token
- 12 Did not find end of ADCON relocatable table
- 16 EXEC statement parameter is invalid
This lists the special parameter value specified for this run. PARM values:
- FSEARCH: Force SPIZAPCK to use the first phase found in the search chain (i.e., negate the effect of message SPI254A). This allows the phase in a private library to be used. This option is not normally used.
The PRODID macro failed for the reason explained by RC=. Name= contains the internal routine name where the error occurred. Check to insure that the proper release of the operating system is installed. Contact Software Pursuits if you cannot quickly resolve the problem.SPI301C MODESET Failure RC= 'xxx', Request=nnnnnnnn
The MODESET macro failed for the reason explained by RC=. Request= contains the internal request code of the function that failed. Check to insure that the proper release of the operating system is installed. Contact Software Pursuits if you cannot quickly resolve the problem.SPI302C Error trying to CDLOAD SPI$SYSX
An error occurred while trying to load the SPI$SYSX phase into GETVIS storage. Check to insure that the proper release of the operating system is installed. Contact Software Pursuits if you cannot quickly resolve the problem.SPI303C PRODEXIT Failure RC= 'xxx', Request=nnnnnnnn
The PRODEXIT macro failed for the reason explained by RC=. Request= contains the internal request code of the function being requested. Check to insure that the proper release of the operating system is installed. Contact Software Pursuits if you cannot quickly resolve the problem.SPI304C Phase 'nnnnnnnn' not found.
The phase specified by nnnnnnnn was not found when it was attempted to be loaded. This phase is required in order to run the product. Check your library search chains. Contact Software Pursuits if you cannot quickly resolve the problem.SPI305C Unable to obtain system GETVIS, RC= 'xx'
A system GETVIS request failed due to the reason specified in RC=xx. Review the cause and take corrective action. Contact Software Pursuits if you cannot quickly resolve the problem.SPI306C Unable to load SPI$ESAX, RC= 'xx'
The loading of the SPI$ESAX phase failed for the reason explained by RC=. Review the cause of the error as specified by the return code. Take the necessary corrective action. Contact Software Pursuits if you cannot quickly resolve the problem.SPI307I SPI$ESAX loaded at X'Addr'
This informational message displays the storage address of the SPI$ESAX module. This module is dynamically loaded into the system GETVIS area during SPI common interface activationSPI308I SPI Savearea is at 'Addr'
This informational message displays the storage address of the SPI savearea in system GETVIS.SPI309I SPISPARM loaded at 'Addr'
This informational message displays the storage address of the SPISPARM phase in the SVA.SPI310I SPIDATE loaded at 'addr'
This informational message displays the storage address of the SPIDATE phase in the SVA.SPI311I SPILBSVA loaded at 'Addr'
This informational message displays the storage address of the SPILBSVA phase in the SVA.SPI312I DOCSMAIN loaded at 'Addr'
This informational message displays the storage address of the DOCSMAIN phase in virtual storage.SPI313I SPRI CAT loaded at 'Addr'
This informational message displays the storage address of the SPRI CAT table in the Virtual storage.SPI314I SPIPLFRT loaded at 'Addr'
This informational message displays the storage address of the SPIPLFRT phase in the Virtual storage.
This informational message is output to indicate the type of memory dump that is contained on the tape. The "dumptype" will be either REAL or VIRTUAL, depending on the type of dump taken.SPI502I THE STANDALONE DUMP PROGRAM IS ENDING NOW
This informational message indicates that the Stand Alone dump is complete and is ending.SPI503I THE STANDALONE DUMP CONTENTS ARE NOW BEING PRINTED
This informational message indicates that the Stand Alone dump is now in the process of being printed.SPI504A -END OF VOLUME- MOUNT A NEW SCRATCH TAPE AND PRESS ENTER
This message indicates that the Stand Alone dump has reached the end of the tape being processed. To continue, mount a new scratch tape on the output drive currently being used and press the ENTER key. The dump will then continue with the new tape.
This message is only produced when assembling a program which contains a Software Pursuits Macro. An error has been detected which is so severe that the processing of the macro must be aborted. Messages prior to this message will describe the nature of the problem.SPI801 value IS AN INVALID VALUE FOR opname
This message is only produced when assembling a program which contains a Software Pursuits Macro. The operand "opname" specified an unacceptable value. Please refer to the documentation for the macro being used.SPI802 value ASSUMED FOR opname
This message is only produced when assembling a program which contains a Software Pursuits Macro. The value for the operand "opname" was omitted or in error. The processing is continuing, but with "value" being used for "opname". Please refer to the documentation for the macro being used.SPI803 opname MUST BE value
This message is only produced when assembling a program which contains a Software Pursuits Macro. The value specified for " was unacceptable and it must be specified as "value". Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.SPI804 opname MUST BE NUMERIC.
This message is only produced when assembling a program which contains a Software Pursuits Macro. The value specified for "opname" was not numeric. Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.SPI805 opname MUST BE value TO endrange CHARACTERS LONG.
This message is only produced when assembling a program which contains a Software Pursuits Macro. The length of the value specified for "opname" was not valid. The message indicates the acceptable lengths allowed for the value. Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.SPI806 opname OPERAND IS INVALID WITH value
This message is only produced when assembling a program which contains a Software Pursuits Macro. The "opnema" operand conflicts with another operand or value, asSPI807 opname MUST BE A VALUE FROM value TO endrange
indicated by "value". Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.
This message is only produced when assembling a program which contains a Software Pursuits Macro. The numeric value specified for "opname" is outside the specified acceptable range of values. Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.SPI808 value INVALID SYNTAX FOR opname
This message is only produced when assembling a program which contains a Software Pursuits Macro. The macro was unable to recognize the format of "value" that was specified for the operand "opname". Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.SPI809 opname IS REQUIRED, BUT WAS OMITTED.
This message is only produced when assembling a program which contains a Software Pursuits Macro. The user failed to code the "opname" operand. Processing of the macro could not be continued. Please refer to the documentation for the macro being used.SPI810 INCORRECT REGISTER SPECIFIED FOR opname
This message is only produced when assembling a program which contains a Software Pursuits Macro. The register number specified for the "opname" operand is outside the acceptable range of register numbers. Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.SPI811 opname REGISTER CONFLICTS WITH OTHER USAGE
This message is only produced when assembling a program which contains a Software Pursuits Macro. The register number specified for the "opname" operand cannot be used because another operand has also specified this same register. Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.SPI812 value SUBOPERAND IS REQUIRED FOR opname
This message is only produced when assembling a program which contains a Software Pursuits Macro. A sub-operand is required for the "opname" operand. The name of the sub-operand is indicated by "value". Additional messages should indicate if processing was continued. Please refer to the documentation for the macro being used.
This message simply reports that the named program has begun execution. The version and modification level are indicated in the message along with an internal reference code. In case of a problem with the program, the contents of the message should be reported to Software Pursuits.SPI901D Duplicate keyword specified
The same keyword was specified twice in the same statement. Check for possible confusion on keyword abbreviations or misspelling. The statement is rejected.SPI902D Too many positional operands
A positional operand was specified for a statement which does not allow the number of positional operands specified or a positional operand was placed after a keyword operand. Check for possible misspelling of a keyword which does not use an equal sign and review possible operands for the statement. The statement is rejected.SPI903D Unpaired parenthesis
The number of left parentheses in the statement does not equal the number of right parentheses. Check for a missing parenthesis. The statement is rejected.SPI905D Unpaired quote
The number of single quote marks in the statement is not an even number. Check for a missingSPI906D Undefined keyword
A keyword was specified as an operand, however the keyword is not recognized for this statement. Check for possible misspelling of the keyword and review the permissible keywords for this statement. The statement is rejected.SPI907D Invalid operand value
The value of an operand is not numeric or does not match one of the possible values permissible for that operand. Review the list of valid operands for each operand coded. The statement is rejected.SPI908D Table specification error
A SCANPARM table error has been detected. Possibly core has been overlaid or a verb table out of order. Obtain a dump and call SOFTWARE PURSUITS technical support.SPI909D Invalid name field
The name field coded for the statement contains too many characters. A name may contain a maximum of eight characters. Check if a name field was intended. Not all commands use a name field. The statement is rejected. To omit a name field, start the verb in column two.SPI910D Verb not recognized
The name of the command entered was not recognized. Check for a misspelling or improper abbreviation of the statement. Some command names (verbs) cannot be abbreviated. The statement is rejected.SPI911D Invalid keyword abbreviation
The abbreviation of a keyword operand was too short and could not be distinguished from other keywords. The operand must contain enough characters to be recognized from other possible operands. Some operands may never be abbreviated or may have minimum lengths associated with their abbreviation. The statement is rejected.SPI912D Invalid operand value
The value of an operand is not numeric or is not one of the permitted values for the operand. Review the permitted operand values for those operands coded. The statement is rejected.SPI920C Too many continuation stmt operands
This error should never occur in normal processing. Too many continuation statements were submitted or too many operands were coded or the combined length of all operands contained too many characters. Shorten the values, code fewer operands, or use fewer continuation statements. The Job is cancelled.SPI981W SPIIFSVA JCL Exit GETVIS failed
An attempt was made to use a JCL exit via the Software Pursuits Common Interface. The exit routine was unable to acquire 256 bytes of partition GETVIS space and is unable to perform any processing. Contact Software Pursuits for assistance.SPI982W SPIIFSVA JCL Exit SUBSID unknown
An attempt was made to use a JCL exit via the Software Pursuits Common Interface. The exit routine was unable to recognize the release of the operating system in use and cannot perform any processing. Contact Software Pursuits for assistance.SPI983W SPIIFSVA JCL Exit JCLE120 scan failed
An attempt was made to use a JCL exit via the Software Pursuits Common Interface. The exit routine was unable to locate critical information in the job control program and cannot perform any processing. Contact Software Pursuits for assistance.SPI984C opname is required, but was omitted.
The user failed to code the "opname" operand. The statement has been rejected. Please refer to the documentation for the statement being used.SPI991C SPIIFSVA is not in SVA or is not initialized.
The common interface phase SPIIFSVA must reside in the SVA. This message is caused either because it is not in the SVA or the common interface is not active. Contact Software Pursuits if you cannot quickly resolve the problem.SPI992C Invalid SPIIF Routine Code.
This is an internal error. Contact Software Pursuits at once.SPI993C Invalid operands passed to SPIIF.
This is an internal error. Contact Software Pursuits at once.SPI994C Task not in valid state for SPIIF call.
This is an internal error. Contact Software Pursuits at once.SPI995C Free List Queue exhausted.
SPI996C SPRI is inactive.
The SPRI spooler is not active or has terminated. A request has been made that requires SPRI to be active. Start up SPRI and retry the failing program. Contact Software Pursuits if you cannot quickly resolve the problem.
Activation of VSE/XRM has begun. The current level of VSE/XRM is also displayed.SPI1001I PRODUCT NOT SUPPORTED
SPI VSE/XRM activation was attempted on an unlicensed CPU. Contact Software Pursuits.SPI1002I SPI COMMON INTERFACE NOT ACTIVE
SPI VSE/XRM activation was attempted without activating the SPI Common Interface first. Activate the Common Interface and then activate VSE/XRM.SPI1003I EXTENDED REAL SIZE ERROR
SPI VSE/XRM activation was attempted on a system that does not have more than 16Mb of real memory. Contact Software Pursuits.SPI1004I INVALID INPUT - input-string
An invalid user option statement was encountered during VSE/XRM activation. Correct the user option statement and activate VSE/XRM.SPI1005I EXTENDED REAL FACILITY NOT INSTALLED
SPI VSE/XRM activation was attempted on a system that does not have the extended real addressing facility installed. Contact Software Pursuits.SPI1006I INITIALIZATION CANCELLED DUE TO ERRORS
SPI VSE/XRM cannot activate due to errors encountered during activation. These error messages have been displayed on the system console. Review error messages and contact Software Pursuits if you cannot resolve the problems.SPI1007I CANNOT LOCATE PAGE FRAME TABLE
SPI VSE/XRM cannot locate the page frame table within the supervisor storage limits. Contact Software Pursuits.SPI1008I PROGRAM CHECK HAS OCCURRED
A program check has occurred in SPI1 during activation. A memory dump will also be produced. Contact Software Pursuits.SPI1009I Unable to PFIX system GETVIS storage
An error occurred while attempting to fix page frames required by VSE/XRM. Activate VSE/XRM prior to starting any other system software. Contact SPI technical support if the problem persists.SPI1010I Cannot acquire nnnK of system GETVIS storage
The real memory required by VSE/XRM during activation could not be acquired. Activate VSE/XRM prior to starting any other system software. Contact SPI technical support if the problem persists.SPI1011I SPIXRMPM LOAD ERROR cc
A VSE/SP load error occurred during the loading of phase SPIERFPM. Insure that phase is in the correct library pointed to by the library search chain.SPI1012ICODE SCAN ERROR cc
A routine could not be located in the VSE/SP supervisor. Contact Software Pursuits.SPI1013I VSE/SP LOGIC ERROR cc
A control table could not be located in the VSE/SP supervisor. Contact Software Pursuits.SPI1014I SVC 191 HOOK SET ERROR
An error occurred during the setting of the supervisor call 191 hooks into the system. Contact Software Pursuits.SPI1015I VSE/XRM MONITOR STORAGE EXCEEDED
More real memory than anticipated is required to activate the VSE/XRM resident routines. Contact Software Pursuits.SPI1016I VSE/SP SERVICE FAILURE cc
A request for VSE/SP services failed during VSE/XRM activation. Contact Software Pursuits.SPI1017I PMA V=R SIZE INCORRECT
The PMA option was specified with a V=R value that was:SPI1018I PMA RMSIZE INCORRECT
- Different from the actual V=R area
- Not a numeric value
Correct the specification and re-IPL the system.
The value specified for the VM RMSIZE was:SPI1019I PMA RSSIZE INCORRECT
- Smaller than the V=R specification
- Greater than 16Mb
- Not a numeric value.
Correct the specification and re-IPL the system.
The value specified for the VM RSSIZE was:SPI1020I REAL MEMORY SIZE: nn.nMG =nnnnnK
- Smaller than that specified on the RMSIZE operand
- Greater than 64Mb
- Not a numeric value.
Correct the specification and re-IPL the system.
The extended real addressing facility has activated under VSE/SP. This message indicates the total real memory size for that VSE/SP system.SPI1021I VSE/XRM SYSTEM INITIALIZED
The SPI VSE/XRM product has completed its activation process successfully. Normal VSE/SP processing continues.SPI1022I VSE/XRM INIT HAS BEEN CANCELLED
An error occurred during the VSE/XRM activation. See previous error messages displayed on the system console. Review previous error messages and take corrective action.SPI1023I PAGE FRAME IN ERROR - error
During the activation of VSE/XRM, a page frame (nnnn) was found to be in error. The indicated page frame will not be used. Normal operation continues.SPI1024I VM/XRM PRODUCT HAS EXPIRED
The VM/XRM product has expired. Contact Software Pursuits.SPI1025I VM/XRM PRODUCT ACTIVATION FAILED
The VM/XRM product has failed to activate. The VM/XRM product has returned an error code to VSE/XRM during the activation of VM/XRM. The guest using VSE/XRM will produce a dump and cancel. Contact Software Pursuits Technical Support.SPI1026I VSE/XRM REQUIRES VM/XRM
An attempt has been made to use the VSE/XRM product on a VM/SP system that does not have the VM/XRM product installed. VSE/XRM requires the presence of VM/XRM to allow extended addressing. This message may also issued if the guest is not running in a V=R area. If the problem persists, contact SPI Technical Support.SPI1027I CP ERROR DURING VM/XRM ACTIVATION
An error has occurred relating to the issuance of specific DIAGNOSE instructions. The failure of these instructions prevents VM/XRM from activating. Contact SPI Technical Support.SPI1028I VM/XRM PHASE 2 ACTIVATION ERROR
An error has occurred during the activation of VM/XRM by the VSE/XRM product. Contact SPI Technical Support.SPI1029I VM/XRM ACTIVATION IN PROGRESS
This is an informational message only. It indicates that the VM/XRM product is in the process of activation.SPI1030I VM/XRM ACTIVATION SUCCESSFULL
This is an informational message only. It indicates that the VM/XRM product has been successfully and proper activated.SPI1031I NO XRM PAGE FRAMES FOR: reason
This is an informational message indicating that no XRM page frames will be used because of an VSE/XRM activation statement. The statements involved are:SPI1032I SPIXRMAR IS NOT IN THE SVA
An attempt has been made to active the VSE/XRM Attention Routine interface. This interface requires the SPIXRMAR phase be in the SVA. You must load this phase into the SVA prior to the activation of VSE/XRM.SPI1033I CANNOT LOCATE $IJBAR SDL ENTRY
The VSE/XRM Attention Routine interface has been selected. However, SPIXRMPI cannot locate the appropriate SDL entry for $IJBAR in the Supervisor. Contact SPI Technical Support.SPI1034I MODULE modname NOT FOUND IN SVA
This message indicates that the indicated module was not found in the SVA during the initialization of the VSE/XRM product. This only occurs when the VSE/XRM EXTMOD=YES control statement is specified. This causes the SVA to be searched for specified phases. If this control statement is used, you must ensure that the indicated phases is loaded to the SVA prior to the execution of the SPIXRMPI program.SPI1035I Cannot locate code for module
EXTMOD=YES was specified and the code scan for the indicated module has failed. Contact SPI Technical Support.SPI1036I VSE/XRM hook set into module
EXTMOD=YES was specified and XRM successfully set the necessary hook for the indicated module.SPI1037I No space available for XRM trace table
The space in that is left over in the old page frame table is too small to create an XRM trace table. No XRM tracing will take place.SPI1038I XRM trace table at X'address' for X'size'
This message indicates the location and size of the XRM trace table.SPI1039I SPIXRMPM loaded at X'address'
This message indicates the location of the SPIXRMPM module in storage.SPI1040I SPIVMX loaded at X'address'
This message indicates the location of the SPIVMX module in CP storage.SPI1041I PFIX request failed R/C=rc
A PFIX request failed with return code shown. Refer to the VSE Messages and Codes publication for a description of the PFIX failure code. If the problem persists, contact SPI Technical Support. This message is usually caused by an inadequate amount of real storage being allocated.SPI1042I $IJBAR scan error location=label
The scan for code at the indicated label in $IJBAR has failed. This error should be reported to SPI Technical Support as soon as possible. You may experience further problems if this is not resolved.SPI1043I VSE/AF supervisor level is: nn.nn.nn
This message indicates the Version/Release/Modification level of the VSE/AF supervisor in use. This information is obtained from the SUBSID macro.SPI1044I Maximum supported address spaces is: n
This message indicates the maximum number of address spaces that can be supported by this VSE/AF supervisor. On VSE/ESA systems running in 370 mode this number represents the number of address spaces supported for static partitions.SPI1045I VSE/XRM AR command interface activated
The AR command interface for VSE/XRM has been successfully initialized and hook in to $IJBAR.SPI1046I INSUFFICIENT V=R AREA TO ALLOW VSE/XRM ACTIVATION
The V=R area is not large enough to allow VSE/XRM to acquire necessary real memory. This problem occurs on VM systems running VSE/XRM with VM/XRM. To resolve the problem, either:SPI1047I SPIXRMST IS NOT IN THE SVA
- Increase the size of the VM V=R (virtual=real) area, or
- Decrease the amount of memory reserved via VSE/SP ALLOCR statement(s).
If your V=R size is 4Mb or more, option 2 is recommended.
The phase SPIXRMST could not be found in the SVA when XRM was activated. This phase is required to be in the SVA.SPI1048I Unable to seize AP/MP processor
During VM/XRM initialization certain hooks must be set into CP code. This process requires that XRM have control of both processors on AP/MP CPUs XRM was unable to seize control of the other processor. The other processor may be looping or stopped functioning. If this problem persists, contact SPI Technical support.SPI1049I Dynamic VM hooks successfully set
The required VM/XRM hooks in the CP nucleus have been set successfully. Initialization continues.SPI1050I Dynamic VM hooks already set
The required VM/XRM hooks in the CP nucleus were found to have been previously set. Initialization continues.SPI1051I Incorrect hardware config - must IML in 4K single key mode
XRM has found that the processor is not IMLed in the proper mode or your hardware does not support the required features for XRM. For XRM to function the CPU must be IMLed in 4K single key mode. If your CE cannot resolve this problem, contact SPI technical support.SPI1052I XRM cannot run without VM on HDS 80xx/90xx CPUs
HDS 80xx and 90xx processors do not support the hardware features required by XRM. To run XRM on these processors you must run under VM with VM/XRM. This is because VM/XRM is able to simulate the necessary hardware requirements. <SPI1053I SPIXRMST successfully initialized
The initialization of SPIXRMST completed normally. Initialization continues.SPI1054I Unable to get REAL supervisor state
VM/XRM initialization requires that VSE/XRM seize control of the system from CP for a brief period of time. VSE/XRM was unable to get this control from CP. Contact SPI Technical Support.SPI1055W SPIIF macro error R/C=rc
An unexpected return code was received from the SPIIF internal macro. This may be caused by having the incorrect level of the SPI Common Interface component. Contact SPI Technical Support.SPI1056W XRM has been deactivated
The XRM product has been deactivated because you have exceeded the system expiration date. You must contact SPI Technical Support to obtain an expiration update. Once the update is applied you must re-IPL your system to re-activate XRM once it has expired.SPI1057C SPIXRMDI CDLOAD ERROR R/C = xxx
A CDLOAD failed for SPIXRMDI. xxx is the VSE/AF CDLOAD Macro return code.SPI1058C SUBSID FAILURE R/C = xxx
A SUBSID Macro failure has occurred.. xxx is the VSE/AF SUBSID return code.SPI1070I XRM Diagnostic Information:
Informational message produced by the XRM DIAG command. Additional information is also displayed. Depending on the circumstances of the display, all output should be saved for SPI.SPI1071I XRM Trace flag is X'ff'
Indicates the value of the XRM trace flag. This is an XRM diagnostic message and should be saved for SPI.SPI1072I XRM environment flags: X'ffffff'
Indicates the value of the XRM internal environment flags. This is an XRM diagnostic message and should be saved for SPI.SPI1073I Total real memory size: nn,nnnK
This message indicates the total amount of real memory in Kilobytes (K) that is being used by XRM.SPI1074I Total pages read from PDS: nn,nnnK
This message indicates the total number of PDS read I/Os that have been issued to the Page Data Set since the system was IPLed.SPI1075I Extended real memory size: nn,nnnK
This message indicates the total number of kilobytes (K) of real memory that XRM is using above the 16 meg line (extended real memory).SPI1076I Total pages written to PDS: nn,nnnK
This message indicates the total number of PDS write I/Os that have been issued to the Page Data Set since the system was IPLed.SPI1077I Overall paging rate: nnn.nn/sec
This is the average paging rate on your system since XRM was initialized.SPI1078I Current paging rate: nnn.nn/sec
This is the paging rate on your system at this particular instant.SPI1079I Normal page frame swaps: n,nnn,nnn
This is the number of page frame swaps that occurred during normal VSE operation.SPI1080I XRM page frame swaps: n,nnn,nnn
This number indicates the number of page frame swaps caused by XRM pages being forced to below the 16m line pages.SPI1081W Unused page frames: nn,nnn
Indicates the number of 4K page frames that are currently unused.SPI1082I Used page frames: nn,nnn
Indicates the number of 4K page frames that are currently in use.SPI1083I No XRM page frames for: component
This message indicates what portions of the VSE system are prevented from using XRM page framesSPI1084I No VSE/XRM APARs [APPLIED | REVOKED]
The XRM APARS AR command has determined that there are no XRM APARs applied to your system.SPI1085I VSE/XRM APAR n.n.nnn [ APPLIED | REVOKED]
This message shows the current status (APPLIED/REVOKED) of the indicated APAR.SPI1086I End of VSE/XRM attention routine display
The requested XRM Attention routine command has completedSPI1087I VSE/XRM installed at APAR level: n.n.nnn
This message displays the level at which VSE/XRM was installed.SPI1088I Hardwait on PCK code: X'cc'
The HARDWAIT=nn initialization command has been issued for program check codes nn. The system will enter a hardwait with PSW DEAD when this program check occurs anywhere in the VSE system.SPI1089I Fixed storage below 16M: nn,nnnK
nn,nnnK represents the amount of real storage below the 16 megabyte line that is currently fixed. This number includes the supervisor itself, any supervisor control blocks that are fixed, pages that have been PFIXed/TFIXed, and programs that are running MODE=REAL. On VM/XRM systems, Fixed storage below the 16M line refers to the storage in the V=R area.
During the printing of the dump, this message is displayed on the operator console. It is asking if the formatted control block information is to printed before the memory contents. Reply "N" to suppress this option. Reply "Y" or enter a null reply to print this section.SPI2101A DO YOU WANT TO PRINT ALL OF VIRTUAL MEMORY? (Y | -N-)
This data contains frequently used information relating to the control blocks for SYSCOM, TIBs, TCBs, Save Areas, etc.
During the printing of the dump, this message is displayed on the operator console. It is asking if all of virtual memory is to be printed. Reply "Y" to print all of virtual memory contained in the dump. Reply "N" or enter a null response to indicates that you wish to select the memory areas to be printed. If "N" is indicated, you will receive message SAD2102A.SPI2102A DO YOU WANT TO PRINT THE SHARED SPACE? (Y | -N-)
During the printing of the dump, this message is displayed on the operator console in response to a "N" reply to message SAD2101A. It is asking if the contents of the shared memory is to be printed. Reply "Y" to print this information. Reply "N" or a null entry to bypass printing of this information.SPI2103A ENTER IDS (Rx) OR REGIONS TO PRINT. EOB TO END SELECTION.
Shared memory includes the Supervisor, the SVA, and all other programs that have a shared space designation.
This message will only appear if you reply "N" to message SAD2102A. During the printing of the dump, this message is displayed on the operator console to ask for the regions that are to be printed.SPI2104I -POINTERS NOT FOUND- PRINTING ALL VIRTUAL MEMORY BY SPACE
Enter the region identification that you wish to be printed. The format is: Rx. Where "x" is the region to be printed (1-9 or A-F). An EOB (null entry) terminates the entry of regions.
If EOB is entered to the first occurrence of this message, no regions are printed.
This message will appear on the operator console if the control blocks required to print the dump by region were not found. This caused the printing to revert to printing by address space.SPI2105I ** THIS DUMP IS A DUMP OF REAL MEMORY ONLY **
This message will appear on the operator console if the dump is of a paging system (S/370 Paging Mode or ECPS Mode). None of the addresses in this type of dump will have been translated.
This message is displayed on the VM system console when VM/XRM has been successfully activated under VM/SP.SPI5002W CP ENTERED; EXTENDED REAL ERROR
This message is displayed on the V=R guest machine system console when a fatal error has occurred in VM/XRM. If this occurs, a standalone dump should be taken on the V=R guest machine for problem determination. Once the standalone dump is taken, the V=R guest machine may be reipl'd.
1500 Fashion Is. Blvd., Suite 205
San Mateo, CA 94404
Copyright © 2000 by Software Pursuits, Inc.