Chapter Contents

Previous

Next
APPLYZAP Error Messages

Messages

The following is a list of notes, warnings, and errors that may be issued by APPLYZAP:


LSCZ000

ERROR: Internal error 0.

Explanation
An internal error occurred. Contact SAS/C Technical Support for assistance.


LSCZ001

ERROR: Error occurred - check log for more information.

Explanation
Additional information about the error is specified in the log.


LSCZ002

ERROR: Comments resemble data - check for missing comma.

Explanation
Comments in a VER or REP statement resemble data. Check to see if a comma is missing. A blank space in the data is treated as the delimiter for a comment.


LSCZ005

ERROR: VER/REP target not in specified CSECT.

Explanation
A VER or REP statement specified a target that could not be found in the CSECT specified by the NAME statement.


LSCZ006

ERROR: Only 1 IDR LOG statement per CSECT is allowed.

Explanation
Only one IDRDATA statement is allowed.


LSCZ007

ERROR: No processing done due to invalid control statements in this set.

Explanation
Look for syntax errors in control statements.


LSCZ008

ERROR: Invalid control file record length (lrecl != 80).

Explanation
When using an input data set for your control statements, ensure that LRECL=80.


LSCZ009

ERROR: Trying to verify/replace non-existent offset.

Explanation
Either a VER or a REP statement specified an offset that does not exist in the CSECT specified by the NAME statement.


LSCZ010

ERROR: Invalid/Incomplete OBJZAP requested.

Explanation
The NAME statement is either incomplete or incorrect. Make sure that the NAME statement specifies a valid member name and CSECT.


LSCZ012

ERROR: Invalid module name specified.

Explanation
The member name specified in the NAME statement is either incomplete or incorrect. Correct the NAME statement and retry.


LSCZ013

ERROR: No CSECT name specified.

Explanation
The NAME statement does not specify a CSECT. Correct the NAME statement and retry.


LSCZ014

ERROR: Invalid CSECT name specified.

Explanation
The NAME statement specifies an invalid CSECT. Correct the NAME statement and retry.


LSCZ015

ERROR: Invalid VER/OFF offset specified.

Explanation
Either VER or REP data was rejected because the offset was invalid. Check to make sure the correct number of digits was specified for the offset and that the offset is valid.


LSCZ016

ERROR: No VER/OFF data specified.

Explanation
The offset for a VER statement is missing. Check VER statements to make sure they all specify an offset.


LSCZ017

ERROR: VER/REP data rejected - invalid.

Explanation
A VER or REP statement was rejected because it contained invalid data. Check VER and REP statements to make sure all data are valid.


LSCZ018

ERROR: VER/REP data rejected - odd number of digits.

Explanation
A VER or REP statement contains an odd number of digits. All VER and REP data fields should contain an even number of digits. Check VER and REP statements to make sure all data are valid.


LSCZ019

ERROR: Not executed. Missing/unsuccessful NAME verb preceded this one.

Explanation
A NAME statement was not executed either because of a missing or invalid NAME statement preceding the statement that was not executed. Check all NAME statements for errors.


LSCZ020

ERROR: Member not found or SYSLIB not defined.

Explanation
OBJZAP could not find the data set member containing the CSECT to be zapped. Check to make sure that the SYSLIB statement specifies the correct data set. Also make sure the specified CSECT is present in the member specified by the NAME statement.


LSCZ021

ERROR: VERIFY NOT SUCCESSFUL: CSECT will not be further modified.

Explanation
The data in the VER statements does not match the data in the module being zapped. Make sure the zap is for the release level of the library being zapped. Also check to make sure you are zapping the correct library.


LSCZ022

ERROR: REP statement not processed due to previous unsuccessful VER/REP.

Explanation
Fix the error that caused the previous VER or REP statement to fail and retry.


LSCZ023

ERROR: Specified CSECT not present in this member.

Explanation
The specified CSECT was not in the member specified by the NAME statement. Make sure you have the correct zap for the release level of the library that you are zapping. Also make sure you are specifying the correct library.


LSCZ024

ERROR: Can only dump the current CSECT and member.

Explanation
A DUMP statement was specified with either an incorrect CSECT or module. Only the current CSECT and member can be dumped. Correct and retry.


LSCZ025

ERROR: This CSECT has already been dumped due to a VER/REP failure.

Explanation
A DUMP statement was specified for the current CSECT; however, a VER error was detected and the CSECT has already been dumped.


LSCZ026

ERROR: IDR data exceeds 10 bytes - a maximum of 10 bytes is permitted.

Explanation
More than 10 bytes of data were specified on the IDRDATA statement. Reduce the data to 10 bytes and retry.


LSCZ027

ERROR: IDR not updated due to missing/unsuccessful REPs.

Explanation
The IDRDATA statement was not executed because a REP statement had not been executed prior to the IDRDATA statement. Either fix the errors in existing REP statement or add at least one REP statement before the IDRDATA statement.


LSCZ028

ERROR: ALIAS name starts with an invalid character.

Explanation
An ALIAS must begin with an alphabetic character or a $, #, or @. Correct the ALIAS statement and retry.


LSCZ029

ERROR: ALIAS name contains and invalid character.

Explanation
The second through final characters of an ALIAS must be either alphabetic characters, numeric characters, or the $, #, or @ characters. Correct the ALIAS statement and retry.


LSCZ030

ERROR: ALIAS name is longer than 8 characters.

Explanation
Correct the length of the ALIAS and retry.


LSCZ031

ERROR: ALIAS name has been specified before.

Explanation
Either remove the redundant ALIAS statement or correct the ALIAS and retry.


LSCZ032

ERROR: ALIAS name cannot be the same as member.

Explanation
Specify an ALIAS for the member and retry.


LSCZ033

ERROR: Can have only 16 aliases for each member.

Explanation
Greater than 16 aliases were specified for a member. Reduce the number of aliases to 16 and retry.


LSCZ034

ERROR: Alias processing: no space in directory.

Explanation
The PDS directory does not contain enough space to add the alias. Increase the amount of directory space allocated for the PDS and retry.


LSCZ035

ERROR: Alias processing: I/O error.

Explanation
An I/O error occurred while writing the alias to the PDS directory. Check the JES log for the cause of the error.


LSCZ036

ERROR: Alias processing: STOW macro failed.

Explanation
An error occurred while attempting to replace an existing alias in the PDS directory. Reallocate the PDS with a larger directory size and retry.


LSCZ037

ERROR: Aliases not replaced as no output operation was performed.

Explanation
A successful REP operation was not performed and the aliases were not updated. Check REP statements and retry.


LSCZ038

ERROR: Checksum error - no output operation was performed.

Explanation
The checksum for the zap does not match the value given by the CHECSUM statement. Check the entire zap for typographical errors and retry.


LSCZ039

ERROR: Not a valid checksum string (8 hex digits).

Explanation
The value argument to the CHECKSUM statement must be 8 hexadecimal characters and cannot contain commas. Correct the CHECKSUM value and retry.


LSCZ040

ERROR: Open failed - additional messages provide more information.

Explanation
A problem occurred while opening the member specified by the NAME statement. Verify that the NAME statement is correct and retry.


LSCZ041

ERROR: Options '-l' and '-a' are mutually exclusive.

Explanation
The -l and -a options are used with OBJZAP on the cross-platform compiler to apply maintenance. (Refer to the installation instructions for more information about these options.) You cannot use both the -l and the -a option at the same time.


LSCZ042

ERROR: AR370 error occurred - Check the archive for correctness.

Explanation
An error occurred when attempting to retrieve the object from an AR370 archive. Use the AR370 utility to verify the integrity of the archive.


LSCZ045

ERROR: LOG zapnum exceeds 8 bytes - a maximum of 8 bytes is permitted.

Explanation
The zap number specified on the LOG statement is greater than 8 characters long. Check the length of the zap number specified and retry.


LSCZ046

ERROR: LOG filetype exceeds 8 bytes - a maximum of 8 bytes is permitted.

Explanation
The filetype specified on the LOG statement is greater than 8 characters long. Check the length of the filetype specified and retry.


LSCZ048

ERROR: BASE Control Record not currently supported.

Explanation
A BASE control statement was specified that is not supported by OBJZAP. Remove the BASE control statement and retry.


LSCZ049

ERROR: ZAP/Control File Not Found.

Explanation
The file containing the zap was not found. Under OS/390, check your SYSIN DD statement to ensure that it is correct and retry. Under UNIX or Windows, make sure you have specified the correct path and name for the input file.


LSCZ050

ERROR: PRINT File Not Found.

Explanation
The PRINT file could not be opened. Under OS/390, check your SYSPRINT DD statement to ensure that it is correct and retry. Under UNIX or Windows, the PRINT output is routed to stdout.


LSCZ200

Zap <zap-name> to module <module-name> in <library-name> applied successfully.

Level: NOTE

ZAP applied successfully.


LSCZ201

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.


LSCZ202

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.


LSCZ203

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.


LSCZ204

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 OS/390, see the job log for more details. Under VM, type HELP on any generated VM message for further details. Also, check SYSPRINT.


LSCZ205

Severe error: <utility-name> RC=nn.

Level: ERROR

Ensure that all zapping utilities needed (that is, under OS/390, 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.


LSCZ206

Fatal error: <utility-name> RC=nn.

Level: ERROR

Check SYSPRINT for a more complete explanation of why the ZAP utility terminated.


LSCZ207

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.


LSCZ208

SYSPRINT not defined or LRECL not 121; or RECFM not FBA.

Level: ERROR

An OS/390 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.


LSCZ209

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.


LSCZ210

Required ddname not defined or defined incorrectly: <DDname>.

Level: ERROR

An OS/390 only error. The <DDname> is not defined to APPLYZAP. See instructions for required DDnames.


LSCZ211

Work file cannot not be created; RC=nn.

Level: ERROR

A temporary work file that is used by APPLYZAP could not be created.


LSCZ212

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.


LSCZ213

Requested Option <option>.

Level: NOTE

An option was requested at run time. The <option> confirms which option was requested.


LSCZ214

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 (OS/390) compare that with the JCL or (VM) ensure that the library is on a write accessed disk.


LSCZ215

Invalid checksum characters; must be 8 hex digits <checksum-value-specified>.

Level: WARNING

CHECKSUM specified is not valid. Verify CHECKSUM value given for correctness.


LSCZ216

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.


LSCZ217

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.


LSCZ218

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.


LSCZ219

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.


LSCZ220

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.


LSCZ221

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.


LSCZ222

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.


LSCZ223

<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 OS/390, issue a DD statement in the JCL for ZAPPED (see JCL examples in Chapter 3). On VM, link the disk that contains the ZAPPED MACLIB as write access.


LSCZ224

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.


LSCZ225

No Memory available - terminating.

Level: ERROR

An attempt to allocate needed memory failed. 4M is the suggested region size under OS/390 and virtual machine size under VM. Check region specification or machine size.


LSCZ226

Writing <ZAPPED | ZAPPED MACLIB> information: <member-name>.

Level: ERROR

An I/O error occurred on the zaps applied data set. On OS/390, this may indicate a need to compress the data set.


LSCZ227

No valid library specified - see APPLYZAP doc for valid libraries.

Level: ERROR

There are no SAS/C libraries defined. On OS/390, 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 accessible disk. See the USING APPLYZAP section under your specific system for valid library names.


LSCZ228

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.


LSCZ229

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.


LSCZ230

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.


LSCZ231

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.


LSCZ232

Error in creation of <ZAPPED | ZAPPED MACLIB>.

Level: ERROR

Creating the zaps applied data set produced an error. Under OS/390 ensure that the DD statement for ZAPPED is correct (see previous JCL examples) and retry. Under VM, ensure that adequate disk space is available and retry.


LSCZ233

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.


LSCZ234

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.


LSCZ235

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.


LSCZ236

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.


LSCZ237

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.


LSCZ238

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.


LSCZ240

No memory available from POOL - terminating.

Level: ERROR

The initial attempt to allocate memory failed. Increase region and retry.


LSCZ241

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.


LSCZ242

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.


LSCZ243

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.


LSCZ244

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.


LSCZ245

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.


LSCZ246

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.


LSCZ247

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.


LSCZ248

Invalid command. Command is ignored - <command>.

Level: WARNING

The specified command is not valid. It will be ignored and processing will continue.


LSCZ249

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 OS/390, 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.


LSCZ250

APPLYZAP command processed - <command>.

Level: NOTE

The APPLYZAP command <command> was processed.


LSCZ251

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.


LSCZ252

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.


LSCZ253

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.


LSCZ254

***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 OS/390 JES log or VM console log before contacting SAS Institute Technical Support.


LSCZ255

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.


LSCZ256

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.


LSCZ258

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 beginning 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.


LSCZ259

Invalid option specified - <option>.

Level: WARNING

The specified option is not a valid APPLYZAP or utility option.


LSCZ260

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 OS/390, 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 accessible 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 accessible disk.


LSCZ261

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".


References

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 © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.