Chapter Contents
Previous
Next
|
Chapter Contents |
Previous |
Next |
| A Guide for the SAS/C Compiler Consultant, Release 6.50 |
The following is a list of
notes, warnings, and errors that may be issued by APPLYZAP:
Zap <zap-name> to module <module-name> in <library-name> applied successfully.
Level: NOTE
ZAP applied successfully.
Zap <zap-name> to module <module-name> in <library-name> applied but generated warnings.
Level: NOTE
ZAP applied successfully, however, it generated warnings. See the ZAP output in SYSPRINT for more details.
Zap <zap-name> to module <module-name> in <library-name>
did not apply.
Level: NOTE
ZAP did not apply. See ZAP output in SYSPRINT for more details.
Zap <zap-name> to module <module-name> in <library-name>
returned a severe error.
Level: NOTE
A severe error occurred in attempting to apply the ZAP. APPLYZAP will not continue. See ZAP output in SYSPRINT for more details.
Severe error returned from <utility-name> attempting to apply <zap-name> to <module-name> :
<library-name>.
Level: NOTE
The utility returned a severe error. Under MVS, see the job log for more details. Under VM, type HELP on any generated VM message for further details. Also,
check SYSPRINT.
Severe error: <utility-name> RC=nn.
Level: ERROR
Ensure that all zapping utilities needed (that is, under MVS, OBJZAP, and AMASPZAP, and under VM, ZAP and ZAPTEXT) are accessible to the program. Also, check
SYSPRINT for a more complete explanation of why the ZAP utility terminated.
Fatal error: <utility-name> RC=nn.
Level: ERROR
Check SYSPRINT for a more complete explanation of why the ZAP utility terminated.
No module name on NAME card - execution cancelled.
Level: ERROR
A NAME card did not contain a module name. Check NAME statements to find the problem.
SYSPRINT not defined or LRECL not 121; or RECFM not FBA.
Level: ERROR
An MVS only error. The SYSPRINT file is used by all zapping utilities. This DDname must be defined and AMASPZAP requires it to have an LRECL of
121.
Zap file write error or out of space - terminating.
Level: ERROR
APPLYZAP could not write to the SYSIN file or not enough space was allocated. Check to ensure proper space allocation and access authority.
Required ddname not defined or defined incorrectly: <DDname>.
Level: ERROR
An MVS only error. The <DDname> is not defined to APPLYZAP. See instructions for required DDnames.
Work file cannot not be created; RC=nn.
Level: ERROR
A temporary work file that is used by APPLYZAP could not be created.
Missing IDRDATA/LOG card - Processing terminated.
Level: ERROR
An IDRDATA or LOG statement was expected and not received. Processing was terminated. Each zap segment begins with a NAME statement and must end with an
IDRDATA or LOG statement. A zap segment has been found that does not contain an ending IDRDATA or LOG statement. Check the zap for errors.
Level: NOTE
An option was requested at run time. The <option> confirms which option was requested.
Library specified in zap does not exist.
Level: ERROR
The NAME statement specified a library that is not valid or was not defined. Check the list printed out with the error message for valid libnames and then
(MVS) compare that with the JCL or (VM) ensure that the library is on a write accessed disk.
Invalid checksum characters; must be 8 hex digits <checksum-value-specified>.
Level: WARNING
CHECKSUM specified is not valid. Verify CHECKSUM value given for correctness.
Checksum error - zap cancelled: <module-name>.
Level: ERROR
CHECKSUM value given was incorrect for zap. Make sure all CHECKSUM statements are in the correct place and have correct values.
Invalid VER/REP offset specified: <VER/REP statement>.
Level: ERROR
Offset value given on VER or REP card is invalid. Make sure value is correct.
VER/REP data rejected - invalid: <VER/REP data>.
Level: ERROR
Data value given on VER or REP card is invalid. Make sure value is correct.
VER/REP data rejected - odd number of digits:
<VER/REP data>.
Level: ERROR
Data value must be given with an even number of hex digits. Make sure value is correct.
No VER/REP offset found - zap cancelled:
<VER/REP statement>.
Level: ERROR
VER or REP card did not contain an offset value. Check VER/REP statement.
No VER/REP data found - zap cancelled:
<VER/REP statement>.
Level: ERROR
VER or REP card did not contain a data value. Check VER/REP statement.
Remaining zap statements discarded due to EOF.
Level: ERROR
A zap statement was found before a valid NAME card was encountered. Make sure zap is specified correctly.
<ZAPPED | ZAPPED MACLIB> not defined.
Level: ERROR
The zaps applied data set, is not defined. This data set must be defined in order for APPLYZAP to execute. On MVS, issue a DD statement in the JCL for ZAPPED
(see the JCL examples in "Using APPLYZAP"). On VM, link the disk that contains the ZAPPED MACLIB as write access.
Cannot update <ZAPPED | ZAPPED MACLIB> information: <member-name>.
Level: ERROR
An error occurred when attempting to update the ZAPPED information. Check SYSTERM for more details.
No Memory available - terminating.
Level: ERROR
An attempt to allocate needed memory failed. 4M is the suggested region size under MVS and virtual machine size under VM. Check region specification or
machine size.
Writing <ZAPPED | ZAPPED MACLIB> information:
<member-name>.
Level: ERROR
An I/O error occured on the zaps applied data set. On MVS, this may indicate a need to compress the data set.
No valid library specified - see APPLYZAP doc for valid libraries.
Level: ERROR
There are no SAS/C libraries defined. On MVS, define the SAS/C libraries with DDnames LOAD, LINKLIB, and so on. On VM,
define the SAS/C libraries by ensuring that the files are on a write accessable disk. See the USING APPLYZAP section under your specific system for valid
library names.
Module does not exist in library: <library-name>.
Level: ERROR
Module found on NAME card does not exist in the specified library. Ensure that the correct libraries are defined.
Diagnostics generated: <utility-name> RC=nn.
Level: WARNING
The specified zap may not have applied. Check the return code given by the zap utility and look at SYSPRINT to obtain an explanation of the
problem.
No library name and AUTO not specified.
Level: ERROR
The NAME statement contains no library specification and NOAUTO is in effect. APPLYZAP cannot apply this zap.
Current zap may not be completely applied.
Level: WARNING
The zap failed to apply to one of multiple libraries; therefore further execution with this zap is terminated. Check SYSPRINT for details on why the zap
failed to apply.
Error in creation of <ZAPPED | ZAPPED MACLIB>.
Level: ERROR
Creating the zaps applied data set produced an error. Under MVS ensure that the DD statement for ZAPPED is correct (see the JCL examples in "Using APPLYZAP") and retry.
Under VM, ensure that adequate disk space is available and retry.
No more ZAPPED information kept.
Level: WARNING
Issued to inform the user that for the remainder of this execution, APPLYZAP will not attempt to keep any information in the zaps applied data set. This is a
direct result of LSCZ232. See that message for more details.
Error applying zap - additional libraries will be bypassed.
Level: WARNING
Issued to inform the user that additional libraries may be bypassed due to a previous error. This is a direct result of LSCZ231. See that message for more
details.
Permanent ZAPPED information cannot be obtained - terminating.
Level: ERROR
The specified library had no permanent ZAPPED information when it should have or the information could not be obtained. See SYSTERM and SYSPRINT for more
details.
Zap name incorrect - check IDRDATA or LOG card - <zapname>.
Level: ERROR
The specified zap name was not correct. It should have the form of "trrrxxxx" where rrr is the release, xxxx is a number from 0000-9999 indicating the zap
number, and t is "Z", "R", or "$". Correct the name in the IDRDATA or LOG card and retry.
Zap already applied - <zapname | Overridden>.
Level: WARNING
The zap has been previously applied. This message may be issued in two separate cases. If an attempt is made to apply a zap that has been previously
applied, this message will be issued and processing of this zap will end unless the OVERRIDE option was specified. If a zap requires a prerequisite zap and the prerequisite zap has been previously
applied, then this message will be issued and processing of the zap will continue.
Prerequisite zap has not been applied - <prereq zapname>.
Level: ERROR
A prerequisite zap, required by the current zap, has not been previously applied. Processing of this zap will end unless the NOPRECK option was
specified.
No memory available from POOL - terminating.
Level: ERROR
The initial attempt to allocate memory failed. Increase region and retry.
Attempt to bootstrap OBJECT module information failed - <SYSZLIN | SYSZLIN TEXT | library-name>.
Level: ERROR
APPLYZAP attempted to create the initial permanent ZAPPED information for the object format library <library-name>. See SYSTERM and SYSPRINT for more
details.
Attempt to bootstrap LOAD module information failed - <library-name>.
Level: ERROR
APPLYZAP attempted to create the initial permanent ZAPPED information for the load format library <library-name>. See SYSTERM and SYSPRINT for more
details.
Attempt to apply permanent zap information failed - <utility-name> RC=nn.
Level: ERROR
APPLYZAP attempted to maintain the permanent zap information and failed. See SYSTERM and SYSPRINT for more details.
Load module zapped information failure - <library-name>.
Level: ERROR
An attempt was made to retrieve the permanent zap information and failed. For more details on the cause of the failure, see SYSTERM and
SYSPRINT.
Processing of zap terminated due to application failure - <zap-name>.
Level: ERROR
One or more VER statements did not verify; therefore, a failure resulted. Either the zap has been previously applied using another utility besides APPLYZAP or
the zap is in error. Ensure that the zap has not been previously applied before calling SAS Institute Technical Support.
Invalid zap number range. Range is 0-9999 - <zap-name>.
Level: ERROR
The last four bytes of the zap name was not in the range of 0-9999. The zap name must contain a number from 0-9999 in the last four bytes in order for APPLYZAP
to process the zap.
Library specified is not of the correct format - <library-name>.
Level: WARNING
The specified library was found to be in the wrong format. For example, APPLYZAP thought that it should have been an object module library, but found that it
was instead a load module library. APPLYZAP will make the internal adjustments and continue processing the zap.
Invalid command. Command is ignored - <command>.
Level: WARNING
The specified command is not valid. It will be ignored and processing will continue.
Unable to open APPLYZAP input file - <DDname | filename>.
Level: WARNING
The specified input file in the INPUT option or the APPLY command could not be opened. Check to ensure that the file exists and that the filename was spelled
correctly. Under MVS, ensure that the SYSLIB DD defines the library in which the file resides. Under VM, if the file is not in a MACLIB, ensure that it has a filetype of ZAP and is on an accessed
disk; if the file is in a MACLIB, ensure that the SYSZLIB FILEDEF defines the MACLIB where the file resides.
APPLYZAP command processed - <command>.
Level: NOTE
The APPLYZAP command <command> was processed.
APPLYZAP command out of sequence.
Level: ERROR
An APPLYZAP command was found within a zap segment. APPLYZAP commands (APPLY, REPORT, or SYSTEM) can only reside outside of a zap segment. Because a zap
segment is bracketed by a NAME statement and an IDRDATA or LOG statement, APPLYZAP commands cannot appear between a NAME statement and an IDRDATA or LOG statement. The command is ignored and
processing of the zap continues.
Zap library file does not exist - SYSZLIB.
Level: ERROR
The INPUT option or APPLY command was processed and the DD for the zap library, SYSZLIB, was not defined. Under VM, this message also indicates that a file
with a filetype of <zap-name> and a filetype of ZAP could not be located on any accessed disk.
Input obtained from - <SYSZLIB(zap-name) | zap-name ZAP>.
Level: NOTE
The zap input was obtained from SYSZLIB(zap-name) or on VM from zap-name ZAP.
***No zap obtained and eof not found*** - terminating.
Level: ERROR
APPLYZAP has failed on an internal error check. Please obtain the listings from SYSZOUT, SYSPRINT, SYSTERM, and the MVS JES log or VM console log before
contacting SAS Institute Technical Support.
Error returned from system routine - <command> RC=nn.
Level: ERROR
The return code nn was returned from the system function when trying to execute the command. Check the particular documentation for information on the
specified commands.
Zap cannot be applied - Original zap not applied <zap-name>.
Level: WARNING
When attempting to apply a removal zap, it was discovered that the original (bad zap) had never been applied. Processing of the zap ends because there is no
need to remove a zap that has never been applied.
Applying current zap(/segments).
Level: NOTE
An APPLYZAP command (for example, APPLY, REPORT, or SYSTEM) has been found outside of a zap segment; however, it cannot be determined if the command is within
the current zap (between 2 zap segments) or if the command is begining a new zap. APPLYZAP commands should not be intermixed with zap statements. This message is issued to inform that the zap may be
incorrectly split.
Invalid option specified - <option>.
Level: WARNING
The specified option is not a valid APPLYZAP or utility option.
Required library on the NAME card does not exist -
<libname
> rc = <rc>.
Level: ERROR
The libname specified in the NAME statement could not be found. On MVS, check to make sure a DD card for <libname > was given in
the JCL. On CMS, if a <.ext > was supplied in the libname, ensure that the corresponding file is on a write accessable disk. On CMS, if the <.ext > was
NOT given on the libname, ensure that a FILEDEF for <libname> is specified and points to a file on a write accessable disk.
AR370 Library Manager issued diagnostics -
<libname
> rc = <rc>.
Level: ERROR || WARNING
Refer to the SYSPRINT and SYSZOUT files for the complete message from AR370 and take the appropriate actions. Also, consult the SAS Technical Report
C-112, "Changes and Enhancements to the SAS/CCompiler, Library, and Debugger, Release 5.50".
IBM (1987), IBM MVS/XA System Programming Library: Service Aids (GC28-1159)
SAS Institute Inc. (1989), SAS/C Compiler and Library User's Guide, Third Edition, Cary, NC: SAS Institute Inc.
|
Chapter Contents |
Previous |
Next |
 Top of Page |
Copyright © Fri Feb 6 08:07:34 EST 1998 by SAS Institute Inc., Cary, NC, USA. All rights reserved.