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 PLF message.
- The assigned number for a give message.
- 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.
- PLF010C RC=cc FUNC=function - MODULE=SPILBSVA
- The requested Library Interface Access service function shown in the message failed with the indicated return code. Processing of the current PROC is terminated.
- PLF011C RC=cc FUNC=function - MODULE=SPRIIF
- The requested SPRI service function shown in the message failed with the indicated return code. Processing of the current PROC is terminated.
- PLF012C RC=cc SIZE=size - GETVIS FAILED
- An attempt to acquire the amount of GETVIS space indicated in the message failed with the return code shown. No access to PROCs in a source statement library is possible until additional GETVIS space is available.
- PLF013C SPILBSVA NOT FOUND IN SVA
- The phase SPILBSVA was not found to be resident in the SVA. No access to PROCs in a source statement library is possible until the phase is loaded into the SVA.
- PLF014W WAITING FOR STATEMENT BUFFERS
- PLF issues this message if system GETVIS is being used to hold PROC expansion output. This feature (the use of system getvis to hold PROC expansion output) was introduced in PLF 3.6 and is controlled by the STMTPOOL= operand of the PLF activation program (SPIPLFON) control card.
This message can mean that PROC expansion in the region, from which the message is issued, must wait until statement buffers become available. However, if no other regions are processing PROCs when the message is issued, the message means that an insufficient number of buffers were allocated via the STMTPOOL= operand and the current number needs to be increased. In both cases, additional buffers should be allocated or, if running SPRI, the feature should be disabled. To disable the feature, specify STMTPOOL=0 or omit the STMTPOOL operand.
- PLF015D PARM VALUE TOO LONG
- The PARM field on the EXEC statement was longer than the maximum length specified at SYSGEN time. Attempt to code the PARM field with fewer characters or request a new nucleus which will allow a longer PARM value.
- PLF016D INVALID FIELD NAME
- The first parameter specified in an AIF or PIF statement is invalid or not defined. Check for misspelling or an improper subscript value. The "CANCELCD" system variable is not valid unless Job Accounting support was generated in your nucleus.
- PLF017D INVALID COMPARE CONDITION
- The second parameter in an AIF or PIF statement contains a compare condition which is not defined. Check for possible spelling errors or for an omitted compare condition.
- PLF018D INVALID VALUE FOR COMPARE
- The value specified in an AIF or PIF statement is improperly specified for the type of compare operation or contains a syntax error. Compare conditions which start with a "B" require a one byte hex value specified by two hex digits. All values must be enclosed in single quotes.
- PLF019D INVALID BRANCH NAME
- The sequence symbol specified as a branch name in an AGO, PGO, AIF, or PIF statement is invalid. A sequence symbol must be from 1 to 8 or 2 to 9 characters in length.
- PLF022D INVALID HEX DATA VALUE
- The hex value specified in a MVCOM, AIF, or PIF statement is invalid. Only an even number of digits 0-9, A-F may be specified.
- PLF023C TOO MANY VARIABLE SYMBOLS
- Too many variable symbols have been defined within a PROC. The Job is canceled. Either some variable symbols must be deleted from the PROC or additional table space must be made available by specifying a larger value for the "INCREASE=" operand of the SPIPLFON "SET" verb.
- PLF024C SPRI IS INACTIVE
- This message is issued if a // PROC statement is processed when SPRI is not active. // PROC statements are valid when SPRI is inactive only if they contain the operand SPOOLOUT=NO.
- PLF025A PROC READ FOR UPDATE/CONTINUE/DATA 'text'
- This message is issued while a // PROC statement is being processed to enter information which would normally be entered in card form. The // PROC statement is normally entered from the console before this message will appear. It might, however, be due to a // DATA statement with an INPUT=SYSLOG operand. The text of the message indicates what created the read. Prompting information may be specified from the PROMPT= operand on a // DATA statement.
The message is prompted by the need to continue the original // PROC statement, the presence of the UPDATE=YES operand, and by // DATA statements. An EOB/END response to a read for a // DATA statement will also serve to indicate end of data, as would a /*. An EOB/END response may be used in place of a ) END statement when performing temporary procedure updates.
- PLF026W SEQ SYMBOL symbol NOT FOUND
- This message is issued as a warning on SYSLST only to indicate that the named sequence symbol was not found in the PROC. The JCL flush operation started by a PGO or PIF statement was terminated at the end of the PROC.
- PLF027C PROC s.procname NOT FOUND
- The PROC requested was not found in any accessible Private Source Library or in the System Source Library in the sublibrary indicated. Check for a misspelling of the procedure name and check that you are pointed to the correct private source library. Remember that procedures are normally unnested when the outermost PROC is processed. If the inner PROCs are in different private source libraries, this error would occur.
- PLF028C INVALID OR MISSING UPDATE CARD
- A PROC was processed with the UPDATE=YES operand and an error was detected in one of the update control statements. An update statement was missing, out of sequence or contained a bad operand (such as a non-numeric sequence number) or an operand was illegal.
- PLF029C UPDATE BOOK s.bookname NOT FOUND
- The book named in a ") BOOK" control statement during an update function for a PROC was not found. Check for a misspelled book name and review a listing of your PROC and the PROCs nested within it. The job is canceled.
- PLF039C &SYSBRCNT EXHAUSTED, TOO MANY BRANCHES.
- Too many branches have been attempted with a procedure. The system variable, &SYSBRCNT, is decremented each time a successful branch is taken and this cancellation occurs when the value reaches zero. This generally means that a loop has occurred within a procedure. If the problem is not a loop, an overriding value may be assigned to &SYSBRCNT with either a PSET, to affect the global variable, or a PLOCAL statement, to set a local value.
- PLF040D UNREFERENCED SYMBOLS SPECIFIED ON PROC STATEMENT PRESS EOB/ENTER TO RUN THE PROC, OTHERWISE ENTER CANCEL.
- The original PROC statement, a nested PROC statement, or a reply to a PREAD statement specified a keyword variable which was never referenced within the procedure. This may be an error if the intended variable was misspelled. This message gives you the chance to recognize a misspelling and terminate the procedure before it is run incorrectly. Note that if the procedure contained multiple JOB statements, some of the jobs may already have been submitted and it is already too late to cancel those jobs.
- PLF041W WAITING FOR STATEMENT BUFFERS
- This message is issued when system GETVIS is being used to hold PROC expansion output (refer to the STMTPOOL= operand of the SPIPLFON program). This message may be issued under 2 conditions:
You may either:
- The amount of buffers allocated via the STMTPOOL= operand is not sufficient (this is generally the case when only a single region issues the message and no other regions are processing PROCS), or
- The region in which the PROC is being processed cannot obtain sufficient statement buffers because other regions are also processing PROCS causing the maximum statement buffers to be allocated.
- Allocate additional statement buffers with the use of the STMTPOOL= operand, or
- If you are using SPRI, disable the feature by coding STMTPOOL=0.
- PLF042W SPOOL ACCESS FAIL. F=aa,RC/RE=bb/cc,PWR RC/FDBK=dd/dd
- An error has been detected in an XPCC Spool Access call used to submit PROC output to the spooler. This message provides information about the request and the error. The information displayed includes the XPCC function code (aa), the XPCC Return and Reason Codes (bb/cc) and the POWER Return and Feedback codes (dd/ee). Processing of the PROC is terminated.
- PLF050C ICCF SUPPORT IS NOT AVAILABLE
- This message is issued when PLF encounters the ICCFLIB= operand on a PROC statement. It indicates that the ICCF access interface DTSIPWR was not found in the SVA. As a result, PLF is not able to retrieve the PROC named in the PROC statement.
- PLF060E ALL JOB ACCOUNTING EXITS DEACTIVATED-EOB TO CONTINUE
- During initialization of PLF, SPIPLFAC was unable to locate the PLF support phase SPIPLFRT in the SVA. EOB will continue the startup of PLF. Please note that because SPIPLFRT is not in the SVA, all of your job accounting exits may not function properly. It is recommended that the required phase be installed in the SVA to assure proper exit functioning.
- PLF100I SPIPLFON(vv.mm-yyyy/mm/dd:hh) AT hh.mm ON mm/dd/yyyy
- This message is output whenever SPIPLFON is executed. It serves to identify the version of the program being executed and shows the date and time of execution. The control card entered is always displayed following this message.
- PLF101I CUSTOMER NUMBER - nnnnnnnn
- Your Software Pursuits eight digit customer number is displayed whenever SPIPLFON is requested to activate PLF.
- PLF102I CUSTOMER NAME --- customer-name
- Your Software Pursuits forty character customer name is displayed whenever SPIPLFON is requested to activate PLF.
- PLF103W PLF EXPIRES IN nnn DAYS
- This warning message is displayed whenever your license for PLF will expire in 30 days or less. No reply is required and activation of PLF continues. You should contact Software Pursuits if you have not yet received an expiration update for PLF.
- PLF104I CPUID=cpuid
- The serial number of your CPU which is returned by the EXTRACT ID=CPUID SVC call is displayed whenever you activate PLF. This may or may not be the true serial number of your CPU. The true serial number is always used for license and expiration checking.
- PLF105I SYSTEM = opsys - V=nn,R=nn,M=nn,FL=xx/xx/xx/xx
- The values returned from a SUBSID INQUIRY,NAME=SUP (or NAME=MVT) SVC call are displayed in this message. The information describes the operating system on which you are running as "MVT/VSE" for the SPI operating system and "VSE/AF" for any of IBM's VSE systems. The version, release, modification and flag bytes values returned are displayed.
- PLF106I SPOOLER = type - V=nn,R=nn,M=nn
- The values returned from a SUBSID INQUIRY,NAME=PWR SVC call are displayed in this message. The information describes the spooling system on which you are running as "SPRI" for the SPI spooling system and "POWER" for IBM's spooling system. The version, release and modification values returned are displayed.
- PLF107I PLF vv.mm.lll/ppp 'xxxxxxx' AT hh.mm.ss ON mm/dd/yyyy - SPIPLFRT(vv.mm) IS LOADED AT X'aaaaaa'.
- The first line of this two line message identifies the installed version, modification level and applied PTF level of the PLF system as well as the function being performed ("STARTED" or "STOPPED") and the current date and time. The second line of the message shows the version and modification level of SPIPLFRT and its address in the SVA.
- PLF108A ENTER SPIPLFON CONTROL CARD
- Whenever SPIPLFON expects to read control cards from SYSLOG it displays this prompt on the console.
- PLF109A INVALID VALUE='value'
- If a value entered for the FUNCTION or INCREASE operands on the SET control card is in error, this message displays the invalid value. Processing is aborted. You must correct the control card value displayed and re-execute SPIPLFON.
- PLF111W SPIZCALL FAILED - REASON = type.
- An attempt to obtain information regarding the installed version level and the applied PTF level has failed because of either an "ERROR" or "SIZE" problem. Processing will continue, but the information shown in message PLF107I will be incorrect. You should contact Software Pursuits Technical Support and inform them of the error.
- PLF112C RC=vm SUP VER/MOD UNKNOWN
- The operating system version modification level shown in the text of the message is not recognized as one on which PLF is supported. Processing is terminated. You should contact Software Pursuits Technical Support for assistance.
- PLF120I CAMLIB ACCESS MODULE (CAMPLFRT) IS LOADED AT X'aaaaaa
- This message is issued during PLF activation via SPIPLFON. It is an indication that PLF was able to locate the CAMLIB access interface routine CAMPLFRT in the SVA. This means that PLF will be able to access procedures that are contained in CAMLIB type libraries. If this message is issued, be sure that the batch program CAMPLFIF has been executed to define CAMLIB search orders.
- PLF130I ICCF ACCESS MODULE (DTSIPWR) IS LOADED AT X'aaaaaa
- This message is issued during PLF activation via SPIPLFON. It is an indication that PLF was able to locate the ICCF access interface routine DTSIPWR in the SVA. This means that PLF will be able to access procedures that are in the ICCF libraries.
- PLF204C RC=cc GETVIS FAILED
- An attempt to acquire region/partition GETVIS space failed with the return code shown. The space is needed to load the PLF table phase SPIPLFTB. PLF functions will not be available in the failing region/partition until GETVIS space can be acquired; the current request is ignored.
- PLF207C SCAN FOR field FAILED
- The PLF system was unable to locate a field in $JOBCTLA which it must be able to access; the identity of the field is shown in the message. The current request is ignored. Contact Software Pursuits Technical Support for assistance.
- PLF800A CONTACT SOFTWARE PURSUITS REGARDING YOUR LICENSE SDCDA=99999,SDCCN=99999999,X'xxxxxxxxxxxx' SDCUL=X'xxxx',X'xxxxxx',X'xxxxxx',X'xxxx',X'xx',X'xx',X'xx'
- This three line message is displayed whenever you attempt to use PLF on an unlicensed CPU or an expired system. One or more Expiration Control System messages (SPI100 through SPI119) which indicate the nature of the error are displayed preceding this message. Refer to the "Software Pursuits Software Support Products User's Guide" for information on those messages. SPIPLFON may or may not continue processing depending on the type of error. If processing cannot continue, message PLF807A will always be displayed after this message. The second and third lines of this message provide additional information which the Software Pursuits Technical Support staff may ask you for to help resolve the problem.
- PLF801C PHASE 'phasename' NOT FOUND IN CIL.
- An attempt to verify the presence of the required phase whose name is shown in the message failed. PLF issued a LOAD DE=YES,TXT=NO for the indicated phase and the system indicated that it was not found. Processing is aborted.
- PLF802C PHASE 'phasename' NOT FOUND IN SVA.
- An attempt to verify the presence in the SVA of the required phase whose name is shown in the message failed. PLF issued a LOAD DE=YES,TXT=NO for the indicated phase and the system indicated that it was not in the SVA. Processing is aborted.
- PLF803C RC=X'xx' ON CALL=call-type
- The hex return code shown in the message indicated an error for the function call identified. In all cases, except for a RC=08 ON CALL=SUBSID-P, the error is fatal and processing is aborted. You should contact Software Pursuits Technical Support for assistance.
- PLF804W PLF IS ALREADY ACTIVE.
- This messages indicates PLF was already active when you specified FUNCTION=ON. The request is ignored.
- PLF805C JCLEXIT LIST EXHAUSTED.
- PLF requested activation as a $JOBEXIT routine from the SPI Common Interface (SPIIFSVA) but was rejected because there are no available entries. Processing is aborted and PLF cannot be activated. Contact Software Pursuits Technical Support for assistance.
- PLF806W PLF IS ALREADY INACTIVE
- This message indicates that PLF was already inactive when you specified FUNCTION=OFF. The request is ignored.
- PLF807A CANNOT PROCESS REQUEST, CHECK SYSLST FOR ERRORS
- This message is written to SYSLOG whenever any error has been detected by SPIPLFON and other error messages were written to SYSLST.
- PLF808A SYSLST IS NOT ASSIGNED, REPLY IGNORE TO CONTINUE?
- If SYSLST is not assigned, this message is written to SYSLOG. If you reply "IGNORE", SPIPLFON will continue execution; all SYSLST error messages will be lost. Any other reply causes the program to terminate immediately.
- PLF812C GETVIS FOR cccccccc FAILED - RC=X'xx'.
- A request for GETVIS storage for the purpose indicated by cccccccc was not successful. The hexadecimal return code is displayed. PLF cannot be activated. If you cannot identify and correct the problem, contact Software Pursuits Technical Support for assistance.
- PLF813C SPIIFSVA must be at level 4.0 or higher on VSE/ESA
- This message indicates a component mismatch. On VSE/ESA systems PLF requires that the SPI Common Interface must be at Release Level 4.0 or higher. Contact Software Pursuits Technical Support for assistance.
- PLF814C SUBSID NOTIFY FAILED - RC=X'xx'.
- A request to obtain privileges using SUBSID NOTIFY failed with the indicated return code. PLF cannot be activated. If you cannot identify and correct the problem, contact Software Pursuits Technical Support for assistance.
- PLF815C LOAD ADDRESS ERROR FOR SPIPLFRT.
- The address returned following a LOAD of SPIPLFRT into PFIXED SVA GETVIS storage is not the expected address. PLF cannot be activated. Contact Software Pursuits Technical Support for assistance.
- PLF816C S$IFPLF IN SPIIFDCT IS NOT ZERO.
- This message indicates either:
- PLF is already active. This request to activate PLF is ignored.
- A previous attempt to deactivate PLF did not complete successfully. PLF cannot be activated. Contact Software Pursuits Technical Support for assistance.
- PLF817W FREEVIS FOR cccccccc FAILED - RC=X'xx'.
- A request to FREEVIS storage which had been acquired for the purpose indicated by cccccccc was not successful. The hexadecimal return code is displayed. PLF deactivation will continue. If you cannot identify and correct the problem, contact Software Pursuits Technical Support for assistance.
- PLF908D TABLE SPECIFICATION ERROR
- This message indicates internal damage to the program or a component mismatch. Contact Software Pursuits Technical Support for assistance.
- PLF909D INVALID NAME FIELD
- This message indicates internal damage to the program or a component mismatch. Contact Software Pursuits Technical Support for assistance.
- PLF913C INVALID CONTINUATION
- A continuation was requested (the previous statement ended with a comma) but the continuation statement was not in the proper format. The statement and the continuation statement are rejected. A continuation statement must start with "//" followed by one or more blanks. The operands may start in any column after the first blank. If a value in quotes is being continued, a starting quote is required to indicate the continuation point of the value.
- PLF920C TOO MANY CONTINUATION CARDS OR PARAMETERS
- Too many continuations were submitted or too many operands were coded or the combined length of all operands contained more than 960 characters. Shorten the values, code fewer operands, or use fewer continuation statements. The job is canceled.
1500 Fashion Is. Blvd., Suite 205
San Mateo, CA 94404
Copyright © 2000 by Software Pursuits, Inc.