Release 5 · 2020. 10. 13. · Conventions Overview 1-4 BIM-ALERT Messages Guide A file containing...

(COPYRIGHT © 1998, B I MOYLE ASSOCIATES, INC.)

BIM--ALERT is a proprietary product of B I Moyle Associates, Inc. It cannot bereproduced, changed, copied, or stored in any form (including, but not limited to, copieson magnetic media) without the express prior written permission of B I MoyleAssociates, Inc.

B I M - A L E R T

CICS AND VSE SECURITY SYSTEM

MESSAGES GUIDE

Release 5.0

This documentation applies to Release 5.0of the program product BIM--ALERT.

Original Printing.......................05/15/98Last Revised .............................05/15/98

Contents iii

ContentsTrademark Information ..................................................................................................... vRelated Publications.........................................................................................................vi

Chapter 1 Introduction.......................................................................................................1-1Overview........................................................................................................................1-2About This Manual ........................................................................................................1-2Conventions ...................................................................................................................1-3

Chapter 2 BIM-ALERT/VSE Messages............................................................................2-1About This Chapter ........................................................................................................2-2Access Authorization Messages .....................................................................................2-3About AXPnnn Authorization Messages .......................................................................2-6AXPSERV Messages ...................................................................................................2-12System Activation/Deactivation Messages...................................................................2-17Logging and Batch Messages.......................................................................................2-26ICCF Submittal Monitor Messages ..............................................................................2-40Rules Assembly and Conversion Messages..................................................................2-42Messages Relating to CA-VOLLIE, DITTO, and Other Programs..............................2-53IPL Exit Messages........................................................................................................2-58Emergency Override Messages ....................................................................................2-60Online Error Messages.................................................................................................2-61Messages from Program AXPU004 .............................................................................2-71Additional Online Error Messages ...............................................................................2-73General BIM-ALERT/VSE Messages .........................................................................2-80

Chapter 3 BIM-ALERT/CICS Messages ..........................................................................3-1About This Chapter ........................................................................................................3-2Initialization Messages...................................................................................................3-3Online Driver Messages ...............................................................................................3-13System Parameter Maintenance Messages ...................................................................3-15Internal Processing Messages.......................................................................................3-16Online File Maintenance Messages..............................................................................3-24Activation and Deactivation Messages.........................................................................3-32Sign-on and Sign-off Messages....................................................................................3-35Batch/Utility Program Messages..................................................................................3-40Informational Messages ...............................................................................................3-58Violation Messages ......................................................................................................3-71

Chapter 4 BIM-ALERT Report Writer Messages ...........................................................4-1About This Chapter ........................................................................................................4-2Report Writer Messages.................................................................................................4-3

Chapter 5 Return Codes .....................................................................................................5-1About This Chapter ........................................................................................................5-2Return Code Descriptions ..............................................................................................5-3File Access Return Codes ..............................................................................................5-3Interval Control Return Codes .......................................................................................5-4Temporary Storage Return Codes ..................................................................................5-5Load Request Return Codes...........................................................................................5-6

iv BIM-ALERT Messages Guide

Storage Request Return Codes .......................................................................................5-6VSAM Error Codes........................................................................................................5-7VSE Cancel Codes .........................................................................................................5-9

Chapter 6 Abend Codes ..................................................................................................... 6-1About This Chapter ........................................................................................................6-2Abend Codes ..................................................................................................................6-3

Trademark Information v

Trademark Information

This manual refers to the following brand or product names, registered trademarks, and trademarks which arelisted according to their respective owners.

Computer Associates International, Inc.:CA-VOLLIE

International Business Machines Corporation:CICSCICS/VSEIBMVM/ESAVSE/ESA

vi BIM-ALERT Messages Guide

Related Publications

This section lists the documentation that deals with BIM-ALERT/VSE and BIM-ALERT/CICS. Your BIM Sales Representative can order any of these documents foryou.

Subject Manual

Installation The BIM-ALERT Installation and Operations Guide explains how to installand maintain BIM-ALERT/VSE.

Using BIM-ALERT

The BIM-ALERT/VSE Security Administrator's Guide explains how to useBIM-ALERT/VSE to set up and maintain security.

Reports The BIM-ALERT Auditing and Report Writing Guide explains how to usethe BIM-ALERT batch report writer.

Messages The BIM-ALERT Messages Guide contains explanations of all messagesissued by BIM-ALERT/VSE.

Subject Manual

Installation The BIM-ALERT Installation and Operations Guide explains how to installBIM-ALERT/CICS.

Using BIM-ALERT

The BIM-ALERT/CICS Security Administrator's Guide explains how to useBIM-ALERT/CICS to set up and maintain security.

Reports The BIM-ALERT Auditing and Report Writing Guide explains how to usethe BIM-ALERT batch report writer.

Messages The BIM-ALERT Messages Guide contains explanations of all messagesissued by BIM-ALERT/CICS.

Overview

BIM-ALERT/VSEManuals

BIM-ALERT/CICSManuals

1-1

1

Introduction

This chapter explains where to find information in this manual and the conventionsused in it.

Overview........................................................................................................................1-2About This Manual ....................................................................................................1-2Conventions ...............................................................................................................1-3

About This Manual Overview

1-2 BIM-ALERT Messages Guide

Overview

About This Manual

This manual contains the following information:

For Explanations of Refer to

BIM-ALERT/VSE messages, which begin with the lettersAX. Most BIM-ALERT/VSE return codes are explained inthe individual message description. All other return codesare explained in Chapter 5, "Return Codes".

Chapter 2, "BIM-ALERT/VSE Messages"

BIM-ALERT/CICS messages, which begin with the lettersGK.

Chapter 3, "BIM-ALERT/CICS Messages"

BIM-ALERT report writing messages, which begin withthe letters ALRT.

Chapter 4, "BIM-ALERTReport Writer Messages"

Several types of CICS and VSE return codes, including fileaccess, interval control, temporary storage, load request,and storage request return codes. Also included aredescriptions of the most common VSAM return codes andVSE cancel codes.

Chapter 5, "Return Codes"

The BIM-ALERT/CICS abend codes that may be producedwhen you try to initialize BIM-ALERT/CICS.

Chapter 6, "Abend Codes"

Overview Conventions

Chapter 1. Introduction 1-3

Conventions

Vertical bars in the left margin (like those opposite this section) indicate significantchanges or additions to, or deletions from, the documentation since the last release ofBIM-ALERT.

The conventions used for all BIM-ALERT/VSE messages are as follows:

• The fixed text of each message is displayed in uppercase.

• The variable text of each message is displayed in lowercase characters. Thelowercase characters most often used to display variable data are as follows:

These Characters Indicate That the Data Is

ccc A return code

X'cc' A hexadecimal return code

nnnnn Numeric

xxxxxxxx Alphanumeric

• When other lowercase characters are used to display variable data, the type ofdata represented is explained in the text describing the message.

Update Bars

BIM-ALERT/VSEConventions

Conventions Overview


A file containing all BIM-ALERT/CICS messages in their default English form issupplied with the product. The message text in Chapter 3, "BIM-ALERT/CICSMessages", reflects this default form, including the placement of all variables. Themessages contain the following two kinds of variables:

Variables Signified By Are Replaced By

VVVVVVVVVVV User-defined variables. Examples of such variables includethe names of types of resources (for instance,TRANSACTION or PROGRAM) or the kinds of departmentsin the company (for instance, DIVISION or SECTION).These user-defined variables need not be in English.

XXXXXXXX Information passed to the message processor by the programrequesting the message. Examples of such information includenumeric data and program names.

Each message in Chapter 3, "BIM-ALERT/CICS Messages", is followed by the keyof the message as defined in the message file; this key appears in parentheses at theend of the message text. To access or update a message directly, enter the key of themessage on the MMSG panel. For more information about updating messages, seethe BIM-ALERT/CICS Security Administrator's Guide.

BIM-ALERT/CICSConventions

2-1

2

BIM-ALERT/VSE Messages

This chapter describes the BIM-ALERT/VSE messages and the actions to take inresponse to them.

About This Chapter....................................................................................................2-2Access Authorization Messages.................................................................................2-3About AXPnnn Authorization Messages ...................................................................2-6AXPSERV Messages...............................................................................................2-12System Activation/Deactivation Messages ..............................................................2-17Logging and Batch Messages ..................................................................................2-26ICCF Submittal Monitor Messages..........................................................................2-40Rules Assembly and Conversion Messages .............................................................2-42Messages Relating to CA-VOLLIE, DITTO, and Other Programs .........................2-53IPL Exit Messages ...................................................................................................2-58Emergency Override Messages................................................................................2-60Online Error Messages.............................................................................................2-61Messages from Program AXPU004.........................................................................2-71Additional Online Error Messages...........................................................................2-73General BIM-ALERT/VSE Messages .....................................................................2-80

About This Chapter


About This Chapter

This chapter describes BIM-ALERT/VSE messages. These messages begin with AXand are divided into the following categories:

Message Numbers Description

AXPnnnI Issued by the access authorization routine and by the loggingprograms.

AXPSRV01x toAXPSRV99x

Issued by the AXPSERV program. These messages apply onlyif you are running BIM-ALERT/VSE under VM.

AX001 to AX035 Related to system activation, system deactivation, and systemoptions.

AX050 to AX209 Generated by the BIM-ALERT/VSE logging and batchprograms.

AX250 to AX255 Generated by the ICCF submittal monitor.

AX301 to AX416 Generated by the rules assembly and conversion programs.

AX417 to AX462 Relate to various BIM-ALERT programs, including the CA-VOLLIE submittal monitor and DITTO command security.

AX495 to AX496 IPL exit messages.

AX497 to AX499 Emergency override messages.

AX500 to AX687 Online error messages.

AX688 to AX696 Messages from program AXPU004.

AX700 to AX765 Additional online error messages.

AX800 to AX899 General messages that can be issued by any BIM-ALERT/VSEprogram.

Access Authorization Messages

Chapter 2. BIM-ALERT/VSE Messages 2-3


SECURITY EXC (variable message text)A security violation occurred, but access was allowed because BIM-ALERT wasrunning in monitor mode. The message text describes the related resource or jobsubmittor. Refer to the description of AXPnnn authorization message formats onpage 2-6 for an explanation of the text of the message.

SECURITY WARN (variable message text)Either a rule requested a console message (the rule had action code W), or BIM-ALERT was running in monitor mode with WTOALL specified. The message textdescribes the related resource or job submittor. Refer to the description of AXPnnnauthorization message formats on page 2-6 for an explanation of the text of themessage.

SECURITY WARN (variable message text)A BIM-ALERT component or an operating system component requested accessauthorization for a type of resource that is not defined to BIM-ALERT. Access wasallowed. The message text describes the related resource. Refer to the descriptionof AXPnnn authorization message formats on page 2-6 for an explanation of the textof the message.

SECURITY EXC (variable message text)A security violation occurred and access was denied. The message text describes therelated resource or submittor. Refer to the description of AXPnnn authorizationmessage formats on page 2-6 for an explanation of the text of the message.

SECURITY FULL (variable message text)A rule requested a log record (the rule had action code L), but the log file was full.Refer to the description of AXPnnn authorization message formats on page 2-6 foran explanation of the text of the message.

The message is issued because the LOGFULL=WTO system option is in effect. Youcan suppress this type of message by specifying LOGFULL=IGNORE. Refer to theBIM-ALERT/VSE Security Administrator's Guide for information about using theSCFL panel to set this system option.

AXP000I

AXP000I

AXP004I

AXP008I

AXP010I



SECURITY STAT (variable message text)Program AXPL3 or program AXPL10 changed the status of the logger. Theseprograms usually run as steps in the log file merge and reporting jobstreams. Themessage provides an audit trail of the status of the logger; it does not require anycorrective action. AXP014I is usually accompanied by one of the followingmessages from the logger: AX062, AX063, AX064, AX065, AX067. These reflectaction taken by the logger in response to the request from AXPL3 or AXPL10. Asample message follows:

AXP014I SECURITY STAT,BG,14.43.33,20,ALTVSE,LOG.START

The fields in the AXP014I message text are separated by commas and appear in thefollowing format:

AXP014I SECURITY STAT,partition,time,serial,jobname,status

The following table describes the positional fields of the message text:

Field Meaning

AXP014I The message reference number.

SECURITY Indicates that the message is a security message.

STAT Indicates that this is a logger status message.

PARTITION The partition where AXPL3 or AXPL10 executed. In the example above, this field has the value BG.

TIME The time, in hh.mm.ss format, when the status change occurred.

SERIAL The log file record serial number.

JOBNAME The name of the job from the // JOB statement.

(continued)

AXP014I



Field Meaning

STATUS The type of change that occurred. Possible values are as follows:

Value Meaning

LOG.CLOSE The logger closed the log file, either in response to a CLOSE commandfrom AXPL3, or because the log file is full, or because the loggerencountered an irrecoverable error that rendered the file unusable.

LOG.FORCE The logger is at end-of-job because a FORCE command was issued throughAXPL3. This status differs from LOG.IDLE because after the FORCEcommand, the logger can be restarted only by restarting the VSE/POWERpartition.

LOG.IDLE The logger has stopped logging. This occurs in the following situations:• When BIM-ALERT/VSE is deactivated• When AXPL3 is executed with the IDLE command• When the log file is full

You can restart the logger in the following ways:

• By activating BIM-ALERT/VSE

• By emptying the log file and running AXPL3 with the RESET commandif logging stopped because the log file was full

• By running AXPL3 with the START command if logging was stoppedby an AXPL3 IDLE command

LOG.INQUIRE AXPL3 has been executed with the INQUIRE command.

LOG.RESET The logger received a RESET command from AXPL3. The logger opensthe log file and begins logging activity.

LOG.RESUME After AXPL10 empties the file, the logger resumes normal logging andissues an AXP014I message with status of LOG.RESUME.

LOG.START The logger has been started. Normally this occurs when BIM-ALERT/VSEis activated.

LOG.SUSPEND When AXPL10 is ready to empty the log file by opening it with reset, thelogger closes the log file and stops writing log requests to the file. While itis in this state, the logger accumulates log requests in the System GETVISarea instead of writing them to the log file. When the logger enters thisstate, it issues an AXP014I message with LOG.SUSPEND as the status.

The logger does not enter this state immediately when AXPL10 begins toexecute, but waits until AXPL10 has completed copying records fromAXPLOG1 to AXPLOG3, and is ready to open AXPLOG1 with reset inorder to empty it. Normally, the logger is in the LOG.SUSPEND state for avery short period of time.

About AXPnnn Authorization Messages



Messages AXP000I, AXP004I, AXP008I, and AXP010I use a common format forthe message text. The fields in the message text are displayed in a positional formatwith the fields separated by commas. The following types of events can producethese messages:

• Job submittor (user) verification• Resource authorization• User authentication

The first positional field indicates which type of event produced the message.Messages produced by job submittor (user) verification can be recognized by theword USERVER in this field.

The following is an example of the message text produced by a job submittorverification or user authentication:

AXP008I SECURITY EXC,USERVER,BG,13.30.34,14,0B,AXPVSE,C,DEVELOP,BIM-ALERT 000C,POW,NO-USER,23,02/18/1998,18:39:04

Messages produced by resource authorization contain the resource class in the firstpositional field. Possible values for this field are CATALOG, DASDDS, TAPEDS,LIBRARY, LIBMEM, SUBLIB, ULTAPE, XCOMRECV, and XCOMSEND.

The following is an example of the message text produced by a resourceauthorization:

AXP008I SECURITY EXC,DATASET,F8,13.28.33,17,1F,AXPVSE,C,DEVELOP,BIM-ALERT 0999,SPL,READ,DBIM-ALERT.XP.TEST.SECURITY.FILE,VSE002

Introduction

Which Type ofEvent Producedthe Message?

Sample MessageProduced By a JobSubmittorVerification or UserAuthentication

Sample MessageProduced By aResourceAuthorization



The positional fields of the preceding messages are as follows:

Field Meaning

AXPnnnI The message reference number.

SECURITY Indicates that the message is a security message.

TYPE Indicates the type of violation that occurred. This field contains one of the following values:

This Value Indicates the Message Was Issued Because

EXC An access violation occurred.

FULL The log file is full and LOGFULL=WTO was specified.

WARN A rule associated with the job or resource had a W (that is, WTO) operand.

CLASS The class of resource to which access was requested. The class is USERVER (for user verification)when an invalid security ID triggers the message, or USERAUTH when the message is triggered duringuser authentication. Other resource classes are those that you define with ALXP (CATALOG,DASDDS, DITTO, LIBRARY, LIBMEM, SUBLIB, TAPEDS, ULTAPE, or XCOM).

PARTITION The partition in which the job requesting access or entry was run. The values for this field in thepreceding examples are BG and F8.

TIME The time, in hh.mm.ss format, when the violation occurred.

SERIAL The rules table serial number of the rule that caused the cancellation. This corresponds to the serialnumber printed on the Rules Conversion Report. If no specific rule caused the cancellation, the messagecontains two commas after the TIME field with no intervening space or serial number.

REASON A reason code indicating the type of rule or rule processing that caused the cancellation. Refer to theBIM-ALERT/VSE Security Administrator's Guide for a list of the reason codes and additionalinformation.

Access can be denied either because of a specific rule or by default when the requesting security ID isnot listed under the ruleset. If access is denied by default, the reason code is 1F and the serial number isthat of the last security ID listed under the ruleset.

USERID The logon ID that submitted the jobstream. Refer to the BIM-ALERT/VSE Security Administrator'sGuide for additional information, including information about internally generated user IDs and pseudo-user IDs.

LOGONSOURCE

The type of session the submittor was logged on to.

SECID The security ID of the job. Refer to the BIM-ALERT/VSE Security Administrator's Guide for additionalinformation, including information about internally generated user IDs and pseudo-user IDs.

(continued)

Fields in theMessages



Field Meaning

JOB NAME The name of the job from the // JOB statement.

SOURCE The job entry source, usually a RDR device address.

MODE How the job entered the system; for example, POW (VSE/POWER reader) or SPL (PUTSPOOL orXPCC macro).

ACCESS The requested level of access, such as EXEC. This field is present only in resource authorizationmessages.

ENTITY The name of the resource to which access was requested (for example, the name of the sublibrary ordataset). For a dataset, the actual name is preceded by D for DASD or T for tape. If BIM-ALERT/VSEdoes not know the actual length of the resource name, this field contains the first eight characters. Thisfield is present only in resource authorization messages.

VOLSER The volume serial number of the dataset. This field is present only in dataset resource violationmessages.

USERID The purported user ID making the request. The value for this field in the preceding example isNO-USER. This field is present only in user verification and user authentication messages.

TABLE The table ID of the active rules table. This field is present only in user verification and userauthentication messages.

DATE The date, in mm/dd/yyyy format, that the active rules table was assembled. This field is present only inuser verification and user authentication messages.

TIME The time, in hh:mm:ss format, that the active rules table was assembled. This field is present only inuser verification and user authentication messages.



The messages produced for CICS and non-VSE signon events have a differentformat than the messages for events from BIM-ALERT/VSE. The following areexamples of this different format:

C2 051 AXP000I SECURITY EXC,TRAN,BG, 11:29:02,L080,EKEHLER,ALXP,OPERATOR_NOT_AUTH (1) (2) (3) (4) (5) (6)

C2 051 AXP000I SECURITY EXC,SIGNON,BG,11:29:02,L080,EKEHLER,INVALID_PASSWORD (1) (2) (3) (4) (6)

The following table explains the numbered fields in the above messages:

Field Meaning

1 The resource class. Valid classes are TRAN, FILE, PROGRAM, and FIELD.

2 Partition ID where CICS runs and the time the event occurred.

3 Terminal ID where the event occurred.

4 CICS user ID.

5 Resource name.

6 Reason the record was written.

IntroductionAXP008I SECURITY EXC messages from BIM-ALERT are often accompanied bymessages from a VSE component. The BIM-ALERT messages are displayed onSYSLOG (the system operator console) and in the partition where the BIM-ALERTlogger runs. The VSE messages are generally displayed on both SYSLOG andSYSLST (the system printer), and in the partition where the security violationoccurs.

This section contains brief descriptions of VSE messages related to batch security.Refer to the IBM publications VSE Messages and Codes, VSE/ESA Messages andCodes, and VSE/VSAM Messages and Codes for complete descriptions of thesemessages.

(continued)

MessagesProduced for CICSand Non-VSESignon Events

VSE MessagesThat CanAccompany BIM-ALERT ViolationMessages



Various Types of Security ViolationsA number of VSE components issue the following message when terminating a jobdue to a security violation:

0S20I UNAUTHORIZED ACCESS REQUEST FOR ...

VSE/POWER SLI ProcessingThe following VSE message may be issued during SLI processing:

1QC1I UNABLE TO PROCESS MEMBER ... RC=0004

Return code 0004 means that the job in which the SLI statement appears is notauthorized at the read access level for the requested library member. A number ofother return code values, not related to security, are also possible for message1QC1I.

VSE Librarian ProcessingAn unauthorized attempt to access, catalog, or delete a library member results in thefollowing message from the VSE librarian:

L163 SECURITY VIOLATION FOR ...

If the attempted operation is to catalog a PHASE member using the linkage editor,the following message is also issued:

2199I ERROR DURING LINKAGE EDITING

Message 2199I is a general message covering many types of linkage editor errors,not just security violations.

(continued)



VSAM ProcessingDuring certain types of VSAM processing, BIM-ALERT performs security checkingwithin VSAM modules. When a violation is detected, BIM-ALERT sets up a returncode that causes processing to be terminated and access to be denied. The returncode that BIM-ALERT sets is the one usually used internally by VSAM to indicatethat password checking failed. The IBM publication VSE/VSAM Messages andCodes uses the terms password checking and password failure to refer to these returncodes.

For example, the following VSE message may be issued during VSAM processing.The X'98' (decimal 152) error code indicates a security violation detected by BIM-ALERT.

4228I ... ERROR X'98' (152)

The following VSE message may also be issued during VSAM processing. Thereturn code 56 and reason code 6 indicate a security violation detected by BIM-ALERT.

4A37I ... CATALOG ERROR DURING IMPLICIT DELETE/DEFINE 56,BM,6

Deleting an Unexpired FileBIM-ALERT's authorization checking for deleting an unexpired file is done in thecommon VTOC handler (CVH). When BIM-ALERT detects a security violation, itsets return code 068 to CVH, which then terminates processing and issues thefollowing message:

4467I CVH PROCESS FAILURE RC=068

Message 4467I is a general CVH message. A return code other than 068 indicatesand error other than a security violation.

AXPSERV Messages


AXPSERV Messages

BIM-ALERT/VSE VM INTERFACE v.rm - aaaaaaaaAXPSERV issues this message when it begins initialization of version v.rm.aaaaaaaa is the name of the module that BIM-ALERT/VSE is running. The modulename is provided as audit information and is one of the following:

Name Description

AXPSERV This module does not support the ENCRONLY option.

AXPSERV2 This module does support the ENCRONLY option.

Refer to the BIM-ALERT Installation and Operations Guide for more informationabout the ENCRONLY option.

(C) B I MOYLE ASSOCIATES, INC. - 1998

AXPSERV issues this message upon beginning its initialization procedures.

WAITING FOR READER...Upon completion of its initialization procedures and after completion of eachSUBMIT request, AXPSERV waits for RDR input, issuing message AXPSRV03I.

mm/dd/yyyy hh:mm PROCESSING ID=aaaa FROM bbbbbbbb TOcccccccc ddddddddAXPSERV issues this message at the start of each SUBMIT request in order toidentify the file being submitted. If AXPSERV rejects a SUBMIT request, it willissue an error message instead of issuing message AXPSRV04I.

mm/dd/yyyy and hh:mm are the date and time AXPSERV read the file. aaaa is theSPOOLID number of the file. bbbbbbbb is the CMS user ID of the SUBMITrequestor. cccccccc and dddddddd identify the target of the SUBMIT request.cccccccc is the node ID and dddddddd is the CMS user ID.

mm/dd/yyyy hh:mm S&F FILE aaaa FROM bbbbbbbb AT cccccccc TOddddddddAXPSERV issues this message when it receives a SUBMIT request via RSCS.

mm/dd/yyyy and hh:mm are the date and time AXPSERV read the file. aaaa is theSPOOLID number of the file. bbbbbbbb is the CMS user ID of the SUBMIT

AXPSRV01I

AXPSRV02I

AXPSRV03I

AXPSRV04I

AXPSRV05I

AXPSERV Messages


requestor. cccccccc is the NODEID where the SUBMIT requestor is located.dddddddd is the CMS user ID of the target of the SUBMIT request.

BIM-ALERT/VSE (AXPSERV) TERMINATINGAXPSERV issues this message when it terminates. Termination may occur whenAXPSERV detects an error during initialization. After successful initialization,while awaiting input from the reader, AXPSERV terminates when anything is typedin at its console.

LOCNODE=aaaaaaaa RSCSID=bbbbbbbbAXPSERV issues this message to identify the local RSCS NODEID (aaaaaaaa) andthe user ID of RSCS (bbbbbbbb).

NETWORKING ID DEFAULTED TO 'RSCS'The IDENTIFY command did not return an RSCSID. AXPSERV is going to useRSCS as the RSCSID.

JCLEXIT NAME=aaaaaaaaThis is an informational message that identifies the name of the program specified inthe JCLEXIT configuration statement.

mm/dd/yyyy hh:mm BIM-ALERT/VSE 5.0x INITIALIZATION COMPLETEAXPSERV issues this message upon completion of its initialization procedures.

mm/dd/yyyy hh:mm INVALID TAG ID=aaaa FROM=bbbbbbbb -DISCARDEDThe RDR file to be submitted has no tag data, and therefore it is not possible forAXPSERV to process the request. This may indicate an error in the AXPSENDEXEC, or a user may be attempting to route SUBMIT requests directly toAXPSERV without using AXPSEND.

mm/dd/yyyy and hh:mm are the date and time AXPSERV read the file. aaaa is theSPOOLID number of the file. bbbbbbbb is the CMS user ID of the SUBMITrequestor.

AXPSRV09I

AXPSRV10I

AXPSRV11I

AXPSRV12I

AXPSRV13I

AXPSRV70E

AXPSERV Messages


mm/dd/yyyy hh:mm DEST NOT DEF ID=aaaa FROM=bbbbbbbb -DISCARDEDThe target of the SUBMIT request is not identified as a valid destination in theAXPSERV CONFIG file's DEST statements. The SUBMIT operation is notperformed because INVDEST PURGE is specified in AXPSERV CONFIG.


mm/dd/yyyy hh:mm ILLEGAL FORWARDING ID=aaaa, FROM=bbbbbbbb- DISCARDEDAXPSERV has received a SUBMIT request via RSCS, but the first line in the file isnot an AXPSERV store-and-forward record. This may indicate that a user hasperformed a remote SUBMIT request without routing the request throughAXPSERV on the originating machine. The SUBMIT operation is not performed.


mm/dd/yyyy hh:mm DEST NOT DEF ID=cccc FROM=dddddddd - SENTThe target of the SUBMIT request is not identified as a valid destination in theAXPSERV CONFIG file's DEST statements. Because INVDEST PASS (notINVDEST PURGE) is specified in AXPSERV CONFIG, AXPSERV performs theSUBMIT operation, but does not insert any // ID statement into the jobstream.

mm/dd/yyyy and hh:mm are the date and time AXPSERV read the file. aaaaaaaa isthe target user ID. bbbbbbbb is the NODEID where the target user is located. cccc isthe SPOOLID number of the file. dddddddd is the CMS user ID of the SUBMITrequestor.

mm/dd/yyyy hh:mm NO JOB CARD ID=aaaa FROM=bbbbbbbb - SENTAXPSERV did not encounter any // JOB statement in the jobstream or the $$ JOBstatement that it did find was not valid. Therefore, AXPSERV did not insert any //ID statement into the jobstream. The SUBMIT operation is performed, but when thejob executes, BIM-ALERT/VSE's job entry verification will use a user ID of NO-USER for the job.


AXPSRV71E

AXPSRV72E

AXPSRV73I

AXPSRV74I

AXPSERV Messages


mm/dd/yyyy hh:mm ENCRYPT ONLY ID=aaaa FROM=bbbbbbbbAXPSERV did not attempt to insert // ID statements into the jobstream, but merelyencrypted ones already present.


mm/dd/yyyy hh:mm UNRESOLVED ID STMT ID=aaaa FROM=bbbbbbbb -SENTAXPSERV encountered a // ID statement that it is unable to encrypt. This is usuallycaused by invalid syntax in the // ID statement, such as a USER= or PWD= operandlonger than eight characters. The SUBMIT operation is performed, but when the jobexecutes, BIM-ALERT/VSE's job entry verification will use a user ID ofINV_USER for the job.


mm/dd/yyyy ORIGIN IS AXPSERV ID=aaaa FROM=bbbbbbbb -DISCARDEDRSCS rejected a file from AXPSERV and routed the file back to AXPSERV'sreader. To avoid repeating this sequence over and over, AXPSERV does not attemptto send the file again but instead discards it.

aaaa is the SPOOLID number of the file. bbbbbbbb is the CMS user ID of thesubmittor.

mm/dd/yyyy hh:mm ID INFORMATION DISCARDEDEither the file to be submitted contained an ID statement that AXPSERV hasdiscarded, or the file's $$JOB statement included a SEC=(userid,pwd) parameter thatAXPSERV has removed.

mm/dd/yyyy hh:mm xxxxxxxxxxxx RC=ccc ID=aaaa FROM=bbbbbbbbA CMS macro or CP command resulted in an unexpected return code. The file hasnot been sent.

xxxxxxxxxxxx is the specific function that failed (for example, SPOOL, PUN, orPUNCHC). The decimal value of the return code is ccc. mm/dd/yyyy and hh:mm arethe date and time AXPSERV read the file. aaaa is the SPOOLID number of the file.bbbbbbbb is the CMS user ID of the SUBMIT requestor.

AXPSRV75I

AXPSRV76I

AXPSRV77E

AXPSRV78I

AXPSRV80E

AXPSERV Messages


mm/dd/yyyy hh:mm ID ALREADY INSERTED ID=aaaa FROM=bbbbbbbbThe JCLEXIT program attempted to insert an ID statement, but AXPSERV hadalready inserted one, so the one from the JCLEXIT program was not accepted.

INVALID CONFIGURATION CARD READ:During initialization, AXPSERV encountered an invalid configuration file statement.The invalid statement is displayed following the AXPSRV90E message. Refer to theBIM-ALERT Installation and Operations Guide for a description of the format andsyntax of these statements.

INVALID USERID ON CONFIGURATION CARD:During initialization, AXPSERV encountered an invalid configuration file statement.The invalid statement is displayed following the AXPSRV91E message. The userID specified in the SECOPR statement is not defined to VM. AXPSERV continues,but reverts to AXPSERV as the security operator user ID. Refer to the BIM-ALERTInstallation and Operations Guide for more information.

LOCNODE NOT SPECIFIED YET - CANNOT PROCESSAXPSERV was unable to determine the RSCS local NODE name (it has not beendefined to VM), and therefore a LOCNODE configuration statement is required.The LOCNODE statement must precede any DEST statements. The current DESTstatement is discarded and initialization continues.

JCLEXIT FILE aaaaaaaa NOT FOUNDThe JCLEXIT program (aaaaaaaa) named in the JCLEXIT configuration statementis not present on any disk accessible to AXPSERV. Either correct the program namein the configuration statement or LINK to the disk where the program resides.

CONFIGURATION FILE NOT FOUND - TERMINATINGAXPSERV requires a configuration file named AXPSERV.CONFIG.A.

AXPSRV81E

AXPSRV90E

AXPSRV91E

AXPSRV92E

AXPSRV93E

AXPSRV99E

System Activation/Deactivation Messages



INVALID OPERAND NEAR COLUMN nnThe operand at or near column nn is not a valid keyword or operand. Refer to theBIM-ALERT/VSE Security Administrator's Guide for detailed information about theformat and syntax of these control statements. Then correct the error and resubmitthe job.

PHASE xxxxxxxx NOT SVA RESIDENTThe phase xxxxxxxx is one of several BIM-ALERT/VSE phases required to beresident in the SVA. The startup program AXPI1 attempts to add SDL entries for allphases required to be in the SVA (you don't have to do any SET SDLs). Therefore,AX002 should occur only when AXPI1's attempt to add the SDL entry failed. Lookfor a previous error message that may indicate why AXPI1 was unable to add theSDL entry. This may be a VSE librarian message such as L170, L171, L172, L173,L174, or L175. If there is no prior message, contact BIM Technical Support forassistance.

EXPECTING CONTINUATION, GOT EOFWhen continuation is indicated but the next read results in end-of-file, the programissues AX004. Continuation is indicated by a comma followed by a blank columnafter the last operand of a control statement. Either correct the control statement sothat it does not indicate continuation or else supply the desired continuationstatement. Then resubmit the job.

VSE SECURITY NOT SUPPORTEDIf you attempt to start BIM-ALERT/VSE on a system that does not support VSEData Security, program AXPI1 issues AX006. BIM-ALERT/VSE cannot be startedif this support is not present. Refer to the BIM-ALERT Installation and OperationsGuide for information about VSE Data Security support.

MODE=ACTIV BUT BIM-ALERT/VSE ALREADY ACTIVEYou have attempted to start BIM-ALERT/VSE, but it is already active.

SYSIPT DATA NOT PERMITTED WITH CARDIN=NOThe control file (AXPCTL) specifies CARDIN=NO, therefore no control statementsare permitted on SYSIPT. Load the SYSIPT control statements into AXPCTL, or

AX001

AX002

AX004

AX006

AX007

AX008



remove the CARDIN=NO from AXPCTL so that SYSIPT control statements arepermitted.

IMPROPER MODULE HEADER. PHASE=xxxxxxxx.Each of the BIM-ALERT/VSE phases contains a standard header. The headercontains data that identify the phase as a specific BIM-ALERT/VSE phase. As partof the startup process, AXPI1 examines the headers of several BIM-ALERT/VSEphases that are supposed to be resident in the SVA and attempts to verify that eachone is actually the desired BIM-ALERT/VSE phase. When this verification processfails, AXPI1 issues message AX009.

The most likely cause of this error is that you have a non-BIM-ALERT/VSE phasethat has the same name as the BIM-ALERT/VSE phase indicated by xxxxxxxx.Display the directories of any libraries ahead of the BIM-ALERT/VSE library in thesearch chain to find the duplicate phase. Then put the BIM-ALERT/VSE libraryahead of that library at BIM-ALERT/VSE startup time.

AXPI1 RUNNING IN ANOTHER PARTITIONThe AXPI1 program is not designed to handle multiple concurrent executions. Itissues a LOCK to ensure that concurrent executions cannot occur. When thisattempt to LOCK fails, it issues AX010. Wait until the other AXPI1 executionfinishes, and then resubmit the job.

AXPI1 xxxxxxxxxx RUN NOT SUCCESSFULAn error has prevented AXPI1 from successfully performing the requested operation.xxxxxxxxxx may be ACTIVATE, DEACTIVATE, or MODIFY, indicating the type ofoperation that was requested. Another error message always accompanies theAX011 message.

AXPI1 xxxxxxxxxx RUN SUCCESSFUL *TEST*This message confirms that the requested operation was successfully completed.xxxxxxxxxx may be ACTIVATE, DEACTIVATE, or MODIFY, indicating the type ofoperation that was requested. If TEST=YES was in force, then the text of themessage includes *TEST*.

INSUFFICIENT SYSTEM GETVISBIM-ALERT/VSE requires work space from the system GETVIS area. AX013indicates that AXPI1 was unable to obtain the required amount of storage. TheSYSLST output contains a message indicating the total amount of system GETVISstorage required. Define additional system GETVIS by increasing the GETVIS

AX009

AX010

AX011

AX012

AX013



parameter of the SVA control statement in your IPL procedure, and then resubmitthe job.

UNABLE TO APPLY PRECEDING MONITOR REQUESTThe number of MONITOR entries has exceeded the maximum of 16.

aaaaaaaa NOT IN SDL/MOVE MODEA SET SDL was done for the BIM-ALERT/VSE transient phase aaaaaaaa, butMOVE was not specified. Do another SET SDL for the phase and specify MOVEmode. Then rerun AXPI1.

AXPI1 is designed to add all the required SDL entries automatically. In some cases,when a manual SET SDL has been done improperly, AXPI1 cannot repair theincorrect entry. For this reason, you should avoid doing SET SDLs for any of theBIM-ALERT/VSE phases.

KEYWORD xxxxxxxx IGNORED ON MODE=MODIFYSome BIM-ALERT/VSE system options may be set only at startup time. If youattempt to modify such an option with an AXPI1 MODE=MODIFY run, then AX018is issued. xxxxxxxx indicates the actual keyword. If you need to change the option,you must shut down BIM-ALERT/VSE (MODE=DEACT), and then start it again(MODE=ACTIV) using the new value for the parameter.

UNABLE TO LOCATE HOOK IN PHASE aaaaaaaaIn order to implement extensions to standard VSE security calls, BIM-ALERT mustlocate specific instruction sequences inside certain VSE components. When theactivate program AXPI1 is unable to locate one of these sequences, it issues AX019and terminates the activation process. aaaaaaaa is the name of the phase thatAXPI1 was processing. If the phase specified is SGACF, AXPI1 was attempting tolocate the SGACF routine inside the Supervisor program.

AX019 usually indicates an error in program AXPI1. Contact BIM TechnicalSupport for further assistance.

BIM-ALERT/VSE NOT ACTIVE, MODE=xxxxxx INVALIDThis message is generated if you try to do a shutdown (MODE=DEACT) or a modify(MODE=MODIFY) when BIM-ALERT/VSE is not active or if the version of BIM-ALERT/VSE that is active is different from the version of the program beingexecuted.

AX014

AX015

AX018

AX019

AX020



UNABLE TO LOCATE TABLE IN $IJJGMSGBIM-ALERT/VSE modifies a table in phase $IJJGMSG, which is resident in theSVA. When AXPI1 is unable to locate this table, it issues message AX021. Thisprobably means that another product has replaced, renamed, or soft renamed thephase. Contact BIM Technical Support for further assistance.

INVALID PRODUCT PASSWORDThe product password that is contained in phase AXPI1 is invalid. Contact BIMTechnical Support for an updated password.

BIM-ALERT/VSE PRODUCT PASSWORD EXPIREDThis message is displayed when the current product password has expired. ContactBIM Technical Support for an updated password.

30 DAYS OR LESS UNTIL EXPIRATIONBIM-ALERT/VSE starts issuing this message when there are 30 days left untilexpiration of your product password. Contact BIM Technical Support for an updatedpassword.

ENTER ANY RESPONSE TO END PROGRAM AXPI1This message follows message AX011 during an activate run. AX011 indicates thatthe activate run was unsuccessful. Message AX026 requests a response from theoperator in order to ensure that the operator is aware of the unsuccessful activate run.After receiving any response to AX026, the program goes to EOJ.

INSUFFICIENT GETVISAXPI1 CDLOADs a number of phases into partition GETVIS and also requires asmall amount of partition GETVIS for work areas. AX027 indicates that there is notenough GETVIS to satisfy these requirements. Rerun the program with a smallerSIZE parameter.

AXPCTL FILE SUCCESSFULLY LOADEDThis message affirms that the file AXPCTL has been successfully loaded.

AX021

AX022

AX024

AX025

AX026

AX027

AX028



CHK$$B MODIFICATION NOT APPLIEDWith SEC=YES, the VSE supervisor prohibits programs from issuing SVC02 (fetcha logical transient phase) for any phase whose name does not start with "$$B". Anyprogram using SVC02 in this manner will be canceled with the VSE message "0S20IUNAUTHORIZED ACCESS". You may choose either to retain or to rescind thisrestriction on the use of SVC02 with the parameter CHK$$. The value you assign tothis parameter will determine the meaning of message AX030.

• If you specified CHK$$B=YES to retain the SVC02 restriction, then messageAX030 is simply a confirmation that this restriction is still in force. BIM-ALERT did not attempt to locate and modify the sequence of instructionsinside the VSE supervisor that enforces this restriction.

• If you specified CHK$$B=NO to rescind the SVC02 restriction, then messageAX030 is an error message. It indicates that BIM-ALERT attempted to locateand modify the sequence of instructions inside the VSE supervisor thatenforces the SVC02 restriction, but was unable to do so.

In this case, get a dump of your VSE supervisor and contact BIM Technical Supportfor resolution of the problem.

The rest of BIM-ALERT activation is completed, even though message AX030 isissued.

UNABLE TO APPLY AXPHJ2 HOOKAXPI1 is unable to locate an instruction sequence inside the supervisor. ContactBIM Technical Support to resolve the problem.

AXPHJ3 NOT ACTIVE IN JCLLUSEXYou are running version 1.2 or higher of VSE/ESA and either you failed to completethe installation step for $JOBEXIT processing or Job Control has disabled your exitlist. Refer to the BIM-ALERT Installation and Operations Guide for furtherinformation.

AX030

AX031

AX031A



BIM-ALERT/VSE v.rr DOES NOT SUPPORT VSE vv.rrVersion v.rr of BIM-ALERT/VSE is incompatible with version vv.rr of VSE, underwhich it is running. The following chart shows BIM-ALERT/VSE versions and thecompatible VSE versions:

BIM-ALERT/VSE Version Is Compatible With VSE Versions

4.60, 4.61, or 4.62 SP2.x, SP3.x, and SP4.x

4.70, 4.71, or 4.72 SP2.x, SP3.x, SP4.x, and ESA 1.1

4.73 SP2.x, SP3.x, SP4.x, ESA 1.1, and ESA 1.2

4.80 SP2.x, SP3.x, SP4.x, ESA 1.1, ESA 1.2, and ESA 1.3

4.91 SP2.x, SP3.x, SP4.x, ESA 1.1, ESA 1.2, ESA 1.3, and ESA2.1

5.0A SP2.x, SP3.x, SP4.x, ESA 1.1, ESA 1.2, ESA 1.3, and ESA2.1, ESA 2.2, ESA 2.3

Check for an old version of BIM-ALERT/VSE in a sublibrary ahead of the currentBIM-ALERT/VSE sublibrary.

MODULE aaaaaaaa bb.cc WRONG VERSION FOR AXPI1 dd.eeThe version of BIM-ALERT/VSE module aaaaaaaa that is resident in the SVA isincompatible with the version of AXPI1 (the activate program) being executed.bb.cc indicates the version of the module and dd.ee indicates the version of AXPI1.Check for multiple copies of the BIM-ALERT/VSE module in your libraries.

If the module identified is $JOBEX00 and you are running version 1.2 or higher ofVSE/ESA, check to be sure you completed the installation step for $JOBEXITprocessing. Refer to the BIM-ALERT Installation and Operations Guide for furtherinformation.

AXPS1 PHASE NOT FOUNDThe LOAD DE for AXPS1 failed. A previous CDLOAD for the same phase did notfail, so AX034 probably represents an internal error or, possibly, library corruption.Contact BIM Technical Support to resolve the problem.

BIM-ALERT/VSE ACTIVATED WITH SEC=NOTAPEThe VSE IPL option SEC=NOTAPE is in force. Therefore, even though BIM-ALERT/VSE is active, and even if rules are defined for tape datasets, BIM-ALERT/VSE will do no security checking for tape datasets. This is a warningmessage. It requires no operator response.

AX032

AX033

AX034

AX039



JOBEXIT WORK AREA NOT LARGE ENOUGH. EXPECTED aaaaa GOTbbbbb. PGM=AXPHP6The work area specified in the PLOAD JOBEXIT command for BIM-ALERT'sPOWER JOBEXIT (RDREXIT) is not large enough. aaaaa indicates the expectedsize of the work area. bbbbb indicates the size of the work area provided byPOWER. For information about using AXPHP6 to increase the size of the work area,refer to the BIM-ALERT Installation and Operations Guide.

PLOAD JOBEXIT,AXPHP6,aaaaa. PGM=AXPHP6B.Program AXPHP6B has issued the PLOAD command to load the BIM-ALERTPOWER JOBEXIT. aaaaa indicates the length of the work area. If you specified alocal exit program, aaaaa includes its work area size as well as AXPHP6’s workarea. This is an informational message. No action is required.

EXEC PARM=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThis message displays the EXEC PARM value used on the AXPHP6B EXECstatement. It specifies the name of the local exit program and its work area size. Ifno EXEC PARM was used, this message displays PARM=NONE.

POWER IS NOT ACTIVE. PGM=AXPHP6B.Program AXPHP6B did not issue the PLOAD command because POWER is notactive.

If this message occurs when executing program AXPHP6B during ASI, it is normalfor POWER not to be active, and no PLOAD is necessary.

If you expected AXPHP6B to issue the PLOAD command, execute AXPHP6B whenPOWER is active.

AXPHP6B NOT REQUIRED FOR PRE-ESA/1.3BIM-ALERT's POWER JOBEXIT is not used in pre-ESA/1.3 systems. Therefore,you do not need to execute AXPHP6B.

INITIALIZATION IN PROGRESS BY ANOTHER TASK. PGM=AXPHP6Because multiple RDR tasks are active, multiple instances of BIM-ALERT'sJOBEXIT are also active. Only one instance of BIM-ALERT's JOBEXIT canperform the initialization process. When this condition is detected, other instances ofthe JOBEXIT bypass all normal processing and return to POWER.

AX040

AX041

AX041A

AX042

AX042A

AX043A



The job that was in progress when this message was issued may receive anUNKNOWN SECID. If this happens, resubmit the job. This condition can beavoided by stopping all POWER RDR tasks before issuing a PLOAD JOBEXITcommand.

JOBEXIT xxxxxxxx LOADED. WORK AREA aaaaa. PGM=AXPHP6.BIM-ALERT's JOBEXIT has successfully loaded the local reader exit program,xxxxxxxx, and has allocated a work area that is aaaaa bytes long. This message is aninformational message. No action is required.

AXPHP6D NOT FOUND OR NOT SVA-RESIDENT. PGM=AXPHP6BIM-ALERT's JOBEXIT either did not find phase AXPHP6D, or it found the phase,but it was not SVA-resident.

If you do not use a local POWER RDR exit, no action is required.

If you use a local POWER RDR exit, BIM-ALERT will be unable to load it as longas AXPHP6D is not SVA-resident. Until this is corrected, no jobs will be processedby your POWER RDR exit. For information on making the JOBEXIT SVA-resident,see the BIM-ALERT Installation and Operations Guide.

BIM-ALERT/VSE POWER JOBEXIT IS ACTIVE. PGM=AXPHP6This is an informational message.

PRODUCT

DEFINE

DELETE ISSUED FOR VERSION v.rr

When BIM-ALERT activates, it identifies itself to the operating system as a vendorsubsystem using the PRODID facility. When it deactivates, it deletes the PRODIDentry. The PRODID facility is available starting with ESA version 1.3.

Message AX044 affirms that BIM-ALERT has taken the indicated action. v.rrindicates the version level of BIM-ALERT that has been activated.

BIMALRTV ENTRY IN BIM-VSR TABLE COMPLETEThis is an informational message.

BIMALRTV ENTRY IN BIM-VSR TABLE *FAILED*Report this message to BIM Technical Support.

AX043B

AX043C

AX043E

AX044

AX046A

AX046B



STOP BIMALRTV IN BIM-VSR COMPLETEThis is an informational message.

STOP BIMALRTV IN BIM-VSR *FAILIE*Report this message to BIM Technical Support.

AX046C

AX046D

Logging and Batch Messages



AXPL1 EXECUTING IN ANOTHER PARTITIONAXPL1 issues a LOCK to prevent multiple concurrent executions of AXPL1. Oncethe logger is started, AXPL1 releases the locked resource.

VSE SECURITY NOT SUPPORTEDBIM-ALERT/VSE cannot be started if VSE Data Security is not supported. Refer tothe BIM-ALERT Installation and Operations Guide for information about VSE DataSecurity support.

XECB=AXPL1 POSTED BUT BIM-ALERT/VSE NOT ACTIVEAXPL1's XECB was posted, indicating that AXPI1 activated BIM-ALERT/VSE, butin fact BIM-ALERT/VSE is still not active. This probably indicates an internalerror. Contact BIM Technical Support for assistance in resolving the problem.

LOGGER ALREADY STARTEDAXPL1 was executed while the logger was already active in some other partition.The logger can be active in only one partition of the system.

aaaaaaa ERROR ON bbbbb R15=cc FDBK=dd ADDR=eeeeeeThis message gives detailed information about a VSAM error on the log file.aaaaaaa is the name of the file. bbbbb is the type of operation that was attempted,such as OPEN or WRITE. cc is the return code from register 15. dd is the feedbackcode. eeeeee is the address in the program where the operation was attempted.

For an explanation of the error code (dd), refer to page 5-7 or to the IBM publicationVSE/VSAM Messages and Codes. Perform the corrective action indicated there.

LOG QUEUE HEADER IS CORRUPTEDThe logger has determined that the log queue header has been corrupted. After thismessage, the logger dumps and then terminates. Contact BIM Technical Support forassistance in resolving this problem.

LOG FILE IS OPENThis informational message is issued as notification that the logger has opened thelog file.

AX050

AX051

AX052

AX053

AX060

AX061

AX062



LOG FILE IS NOT OPENThis informational message is issued in response to an AXPL3 INQUIRE andindicates that the log file is not open. The logger closes the file in response to aCLOSE or IDLE command from AXPL3, and when the log file fills or becomesunusable for some other reason.

LOG QUEUE: aa/bb/cc/dddddd/eeeeeeThis message reports statistics about the log queue, which has a fixed size that isestablished at the time BIM-ALERT/VSE is activated. The data in the message isdisplayed in positional format, with a slash (/) separating each data field from thenext.

aa is the number of entries in the log queue. This is the maximum number of logrequests that can be queued at a time.

bb is the number of pending log requests in the queue.

cc is the greatest number of pending log requests ever in the queue at any one time.

dddddd is the total number of log requests that have been processed by the log queuemanager.

eeeeee is the number of times tasks were put log queue bound. When the log queuefills faster than the log queue manager can empty it, a task that requests logging isput into a wait state until space becomes available in the log queue.

LOG CHAIN: aaaa/bbbbbb/cccc/dddddd/eeeeee/ffffffThis message reports statistics about the log data chain. This chain is of variablesize and is dynamically allocated in the system GETVIS area. The log queuemanager program places log requests on the log data chain, and the log file I/Oprogram writes them to the log file.

The data in the message is displayed in positional format, with a slash (/) separatingeach data field from the next.

aaaa is the number of records currently on the log data chain, waiting to be writtento the log file.

bbbbbb is the amount of storage occupied by the records currently on the log datachain.

cccc is the maximum number of entries ever on the log data chain at any one time.

dddddd is the maximum storage ever occupied at any one time by records on the logdata chain.

AX062A

AX062B

AX062C



eeeeee is the system GETVIS storage threshold. When the amount of availablesystem GETVIS storage drops below this amount, the log queue manager begins todiscard log queue data instead of putting the request on the log data chain.

ffffff is the amount of remaining system GETVIS storage. This is calculated from thenumber of unused pages available for system GETVIS, and will usually be less thanthe overall amount of storage available.

BYPASS: aaa/bbbb/cccccc/mm.dd.yyyy hh.mm.ssThis messages reports whether the logger is currently discarding log data because ofa storage shortage condition, and whether it has ever discarded log data for thisreason.

aaa may have either of two values. YES indicates that the logger is currentlydiscarding log data due to a storage shortage condition. NO indicates that the loggeris not currently discarding log data.

bbbb is the number of times a storage shortage condition has occurred and the loggerhas begun discarding log data. If this condition has never occurred, NONE is shownhere.

cccccc is the total number of log records that have been discarded due to a storageshortage condition.

mm.dd.yyyy and hh.mm.ss show the date (month, day, year) and time (hour, minute,second) of the last time the logger began discarding data due to a storage shortagecondition.

LOG FILE HAS BEEN CLOSEDThis is an informational message issued by the logger when it closes the log file.

LOG FILE IS FULLThis message indicates that the log file is full. No further logging can occur until thefile has been emptied. Refer to the BIM-ALERT Installation and Operations Guidefor additional information about the log file.

LOG FILE IS NOT CURRENTLY OPENThe logger received a CLOSE request from AXPL3, but the file is not currentlyopen. This is an informational message; no corrective action is required.

AX062D

AX063

AX064

AX065



LOG FILE IS FULL OR UNUSABLEThe log file is full, or an irrecoverable I/O error has occurred on the log file.Logging is suspended until the log file is emptied or the error condition is cleared up.

NO PHASENAME SPECIFIEDAXPL9 was executed in a dedicated partition with a phase name of blanks specified(PARM=' '). This mode is normally used only for testing; AXPL9 is designed toactivate the logger and then fetch the VSE/POWER phase specified. If you want torun the logger in a dedicated partition, you should execute AXPL1 rather thanAXPL9.

LOG DATA DISCARDEDThe logger uses system GETVIS storage for log record buffers. This storage isunavailable to other tasks in the system until the log file I/O task writes the recordsto the log file. To safeguard against using up all the available system GETVISstorage, the logger calculates the amount of storage available each time it receives alogging request. If the amount falls below a certain minimum, the logger executesthe following steps:

Step Logger's Action

1 It issues message AX069.

2 It discards the data for the current logging request instead of allocating storage for itin the system GETVIS area as it normally would do.

3 It frees any storage allocated for previous log requests that have not yet been pickedup by the log file I/O task.

4 It stops allocating system GETVIS storage on subsequent logging requests.

The logger continues in this manner until available system GETVIS rises above theminimum, at which time the logger resumes normal logging activity. During thisperiod, the AX069 message is repeated at one-minute intervals.

If this condition occurs frequently, you probably need to increase your systemGETVIS allocation. Do this by increasing the GETVIS parameter of the SYS IPLstatement and adjusting the ALLOC statements for one or more partitions.

Even if the system GETVIS allocation is adequate, this condition can be caused by a"runaway" task repeatedly fetching or loading a program if that program's BIM-ALERT rule specifies logging (ACTION L).

AX067

AX068

AX069



NORMAL LOGGING RESUMEDThe logger has resumed normal logging activity after discarding log data whilesystem GETVIS storage was unavailable. Refer to the explanation of messageAX069 for more information.

AXPL2A TERMINATING - AXPL2B ABENDThe log file I/O task AXPL2B abended. Since logging is no longer possible, the logqueue manager AXPL2A is terminating.

Investigate the cause of the AXPL2B abend and take corrective action asappropriate. It is likely that the source of the abend in AXPL2B is a programmingerror in that program. If that appears to be the case, contact BIM Technical Supportfor assistance in resolving the problem.

AXPL2x ABEND at aaaaaaaa, CANCEL CODE=ccAXPL2A or AXPL2B has terminated abnormally at location aaaaaaaa. The VSECANCEL CODE describes the exact cause of the termination (program check,operator cancel, etc.). Before terminating, the program obtains a dump of thepartition. If OPTION SYSDUMP is in force and a LIBDEF DUMP is in effect, thedump is placed in the dump library. Otherwise, the dump goes to SYSLST.

UNABLE TO OBTAIN LOGGER STORAGE IN PROGRAM AXPS1mm/dd/yyyy hh:mm:ssAXPS1 requested storage for a log record in the system GETVIS area, but theoperating system returned a short-on-storage indication. The log data was discarded.This message is issued by the logger task.

When system GETVIS storage is short, it is likely that AXPS1 will receive the short-on-storage indication over and over again. To avoid flooding the operator consolewith a large number of these messages, the logger task displays the message onlyonce per minute, regardless of how often the condition may have occurred.

mm/dd/yyyy and hh:mm:ss indicate the time that the shortage occurred, not the timethe message is displayed.

LOG DATA DISCARDED BECAUSE THE LOGGER IS INACTIVEmm/dd/yyyy hh:mm:ssIf the logger is not active, BIM-ALERT security checking still builds log records andqueues them in the system GETVIS area in the normal way. BIM-ALERT continuesto queue this log data while the logger is inactive, until a certain threshhold isreached, at which time it stops queueing the data and begins discarding it.

AX069A

AX070

AX071

AX072

AX073



When the logger task starts, it issues message AX073 if that condition occurredwhile the logger was not active. The mm/dd/yyyy and hh:mm:ss reflect the time thatBIM-ALERT began discarding data, not the time that the message is issued.

AXPL3 xxxxxxxx INVALID COMMANDxxxxxxxx is not a valid command for AXPL3. Refer to the BIM-ALERT Installationand Operations Guide for a description of the AXPL3 commands.

AXPL3 aaaaaaaa COMMAND NOT POSSIBLE, LOGGER IS bbbbbbbbaaaaaaaa is a valid AXPL3 command, but because of the state of the logger, itcannot be performed at this time. For example, the FORCE command cannot beperformed if the logger is not currently ACTIVE or IDLE.

AXPL3 STATUS OF LOGGER IS xxxxxxxxxThis message is issued in response to an INQUIRE command to AXPL3. xxxxxxxxxis the status of the logger and may be any of the following:

Status Meaning

ACTIVE The logger has been activated. As log requests are received, the logger willwrite records to the log file, the operator console, or both.

INACTIVE The logger is not receiving log requests either because it was never activatedor because it was activated and subsequently shut down with an AXPL3FORCE.

IDLE The logger was activated, but it was subsequently placed in an idle state byan AXPL3 IDLE command. Log requests are ignored when the logger isIDLE.

If the logger is active, it also issues either message AX062 LOG FILE IS OPEN orAX062A LOG FILE IS NOT OPEN. If the log file is full, the logger issues AX067LOG FILE IS FULL.

ENTER NEXT AXPL3 COMMANDWhen AXPL3 is executed from the operator console, this message indicates that theprogram is ready for another command.

BIM-ALERT/VSE IS NOT ACTIVENone of the AXPL3 commands are possible if BIM-ALERT/VSE is not active.

AX100

AX101

AX102

AX103

AX104



aaaaaaa ERROR ON bbbbb R15=cc FDBK=dd,ADDR=eeeeee,KEY=ffffffffffffffffffThis message gives detailed information about a VSAM error. aaaaaaa is the nameof the file. bbbbb is the type of operation attempted, such as OPEN, CLOSE, orREAD. cc is the return code from register 15. dd is the error feedback code. eeeeeeis an address in the program where the operation was initiated. ffffffffffffffffff is therecord key, if any, that was involved in the operation.

For an explanation of error code dd, refer either to the description of VSAM errorcodes on page 5-7 or to the IBM publication VSE/VSAM Messages and Codes.Perform the corrective action indicated there.

MORE RECORDS ON FILE ... PRESS ENTER TO CONTINUEThere are additional records that satisfy your DLOG selection criteria. PressENTER to see the next screen of records.

END OF SELECTED LOG RECORDSAll the records that satisfy your selection criteria have been displayed. You canproceed in any of the following ways:

• Press ENTER or PF12 to return to the DLOG Selection Criteria Screen.• Press PF3 to return to the ALXP Main Menu.• Press PF10 to go to the PLOG Selection Criteria Screen.

NO SPECIFIED LOG RECORDS IN THE FILENone of the records in the log file satisfies your selection criteria, so there is nothingfor DLOG to display. To try different selection criteria, specify the new criteria andpress ENTER. If you don't want to try different selection criteria, you can proceed inany of the following ways:

• Press PF3 to return to the ALXP main menu.• Press PF10 to go to the PLOG Selection Criteria Screen.

INVALID PRINTER-ID SPECIFIED ... RE-ENTERThe printer specified on the PLOG Screen is not defined in the TCTTE as a printer.

INTERVAL CONTROL ERROR - EIBRCODE = X'cc'. PGM=AXP192.An abnormal return code was received in response to the interval control request tostart task A196 (print log records). Therefore, the request cannot be honored. Referto page 5-4 to determine the meaning of the interval control return code X'cc'. If the

AX160

AX161

AX162

AX163

AX164

AX165



value of the code is X'11', the most likely cause of the error is that you have notdefined transaction A196 in the PCT.

PRINTER UNAVAILABLE FOR PRINTINGThe printer specified on the PLOG Screen has been flagged in the TCTTE asunavailable (out of service, etc.), and therefore the print request cannot be honored.

ERROR ACCESSING SECURITY FILE S1SCTY - EIBRCODE = X'cc'.PGM=AXP192.An error occurred during an attempt to access the BIM-ALERT/CICS security file.Refer to page 5-3 for the meaning of the file access return code X'cc'.

ERROR ACCESSING LOG FILE AXPLOG1 - EIBRCODE = X'cc'.PGM=AXP192.An error occurred during an attempt to access the log file. Refer to page 5-3 for themeaning of the file access return code X'cc'.

INVALID DATA, RE-ENTER - XXXXXXXXXXXXXXXYou entered invalid data on the DLOG or PLOG selection criteria screen. Thespecific field in error is named in the error message in place of "XXX...XXX", andthe field is shown in high intensity. Correct the data and press ENTER.

SELECTED LOG RECORDS NOW BEING PRINTEDAll log records that satisfy the input criteria have been formatted and sent to thespecified printer for printing.

AXPLOGPURGE RESOURCE NOT AVAILABLEWhen DLOG or the report writer requests shared ownership of the AXPLOGPURGEresource while AXPL10 owns it exclusively, the DLOG or report writer task issuesAX171 and terminates.

Wait until the log file purge operation completes, and then initiate your DLOG orreport request again.

Log File Purge Enqueue Mechanism

AXPL10 and other programs that access the log file use the VSE LOCK mechanismto control ownership of a resource named AXPLOGPURGE. This provides asystematic method of testing for and resolving conflicting access requests to the logfile.

AX166

AX167

AX168

AX169

AX170

AX171



Only BIM-ALERT programs implement this AXPLOGPURGE locking mechanism.If you use any other programs, such as CEMT, to open and manipulate the log file,you may encounter problems if the file is left open while AXPL10 is executing; seethe description of message AX171F.

BIM-ALERT programs implement this locking mechanism as follows:

• Read-only tasks, such as DLOG and the BIM-ALERT batch report writerprogram, request a shared lock before opening the log file. This shared lockprevents AXPL10 from running while any of those read-only tasks are running,but it enables multiple read-only tasks to run concurrently. The logger can alsorun concurrently with read-only tasks, adding records to the log file while read-only tasks are reading the file.

• AXPL10 uses an exclusive lock, as follows:

− At the beginning of the log file purge process, AXPL10 opens the log file(AXPLOG1) for read access and copies it to the cumulative log file(AXPLOG3). While this copy operation is in progress, the logger still hasthe log file open for output, and it may add records to the log file. At theend of the copy operation, AXPL10 signals the logger to temporarily closethe log file and to suspend logging operations, so that AXPL10 can copyany records that have been added, close the log file, and then open it withRESET to empty it. In order to do this open with RESET, AXPL10 musthave exclusive control of the log file; no other task is permitted to have thelog file open for any level of access.

− Before beginning the copy operation, AXPL10 issues an exclusive lockrequest for the AXPLOGPURGE resource. This ensures that it will be ableto gain exclusive control of the log file, once it completes the copyoperation. If DLOG or the report writer has the file open for read accesswhen AXPL10 requests the exclusive lock, AXPL10's lock request isdenied; AXPL10 does not proceed until some action is taken to release thelocked resource. Similarly, once AXPL10 owns the resource exclusively,if DLOG or the report writer requests the shared lock, that request isdenied, and the DLOG or report writer task does not proceed.

R=RETRY,C=CANCEL,G=GO AHEAD WITHOUT LOCK - AXPL10If AXPL10 requests the exclusive lock and a DLOG session or a batch report requestis active, AXPL10's request is denied and AXPL10 issues messages AX171 andAX171A. AX171A requests a response from the system console operator. See page2-33 for information about the log file purge enqueue mechanism.

The system operator should respond to AX171A as follows:

AX171A



• If you can confirm that a DLOG session or a batch report request is in progress,and you wish to have the AXPL10 job wait until the DLOG or report operationis complete, respond R. See the description of message AX171D (below) formore information about what happens after you respond R.

• If you believe that no DLOG session or report request is in progress but you arenot absolutely certain, do not respond to the message immediately. Instead,perform the procedure described in the section "Releasing theAXPLOGPURGE Resource," below. Then respond R and AXPL10 will retrythe lock request.

• If you are absolutely certain that no DLOG session or report request is inprogress, respond G to direct AXPL10 to proceed with the purge operationwithout gaining exclusive ownership of the AXPLOGPURGE resource.

WARNING!

Do not respond G unless you are absolutely certain that no DLOG session or batchreport request is currently in progress, and unless you can ensure that none will startwhile AXPL10 is running.

If you respond G when a DLOG session or a batch report request is in progress, theAXPL10 job will copy all the records from the AXPLOG1 file to the AXPLOG3file, it will attempt to open the AXPLOG1 file with RESET, and it will thenterminate, because the open with RESET will fail. The records copied will thenexist in both AXPLOG1 and in AXPLOG3, with no way to purge these recordsexcept to delete and redefine the files.

• If you want to terminate the AXPL10 job, respond C. The job is canceledbefore any part of the log file purge operation has been performed. No recordsare copied from AXPLOG1 to AXPLOG3, and no records are purged fromAXPLOG1.

Releasing the AXPLOGPURGE ResourceIf you receive AX171 while executing program AXPL10, and no DLOG or reportwriter task is currently active, it is likely that a DLOG task locked theAXPLOGPURGE resource and then terminated abnormally, leaving the resourcelocked. This can happen if DLOG abends, or if a DLOG session is signed off byBIM-ALERT/CICS due to inactivity.

To release the AXPLOGPURGE resource, perform the following steps in thepartition where the DLOG task terminated abnormally. If you are uncertain whereDLOG terminated abnormally, perform this procedure in every CICS where you useDLOG.



Step Action

1 Sign on to CICS.

2 Execute the ALXP transaction.

3 Select the DLOG subfunction of ALXP.

4 When the DLOG selection screen appears, press PF3, which returns you to theALXP menu. Returning from DLOG to ALXP should release the AXPLOGPURGEresource.

5 Use CEMT to close the AXPLOG1 file to CICS.

In dire circumstances, when the above steps are not possible, or when they do notseem to release the resource, the resource can be released by terminating the CICSpartitions where you use DLOG.

PROCEEDING WITHOUT LOCKING AXPLOGPURGE - AXPL10When you respond G to the AX171A message, AXPL10 issues message AX171B toaffirm that this action has been taken. This message is for information only and doesnot require the user to take any action.

CANCELLED DUE TO OPERATOR REQUEST - AXPL10When the operator responds C to the AX171A message, AXPL10 issues messageAX171C and cancels the job. This message is for information only and does notrequire the user to take any action.

WAITING ON AXPLOGPURGE RESOURCE - AXPL10After receiving the R response to message AX171A, AXPL10 repeatedly issues thelock request at 10 second intervals. While AXPL10 is in this state and is unable togain exclusive ownership of the resource, it issues message AX171D every 2minutes.

The purpose of AX171D is to keep the operator informed of the status of AXPL10.The message does not require any operator response.

While AXPL10 is in this state, it is safe for the system operator to cancel the job byissuing the AR CANCEL command. If canceled in this manner, the job terminatesbefore AXPL10 has performed any part of the log file purge operation. No recordsare copied from AXPLOG1 to AXPLOG3, and no records are purged fromAXPLOG1.

AX171B

AX171C

AX171D



AXPLOGPURGE RESOURCE OBTAINED - AXPL10After receiving the R response to message AX171A, AXPL10 issues messageAX171E when it finally gains exclusive ownership of the AXPLOGPURGEresource.

The purpose of AX171E is to inform the operator that AXPL10 is no longer waitingfor the AXPLOGPURGE resource. The message does not require any operatorresponse.

R=RETRY C=CANCEL - AXPL10If some task other than DLOG or BIM-ALERT's report writer has the log file openwhen AXPL10 attempts to open the file for reset, this attempt will fail. After issuingmessage AX060 (FDBK code 'A8'), AXPL10 issues message AX171F and waits fora response from the system console operator.

If you know which task has the log file open, wait until the task terminates and thenrespond R to retry the open. If a CICS session has the file open with CEMT, closethe file with CEMT and then respond R at the system operator console to directAXPL10 to retry the open.

WARNING!

If you do not know which task has the log file open, or if you are unable to wait untilthat task terminates, respond C to cancel the AXPL10 execution. In this case, somerecords have been copied from AXPLOG1 into AXPLOG3, and AXPL10 has notremoved these from AXPLOG1. Eventually, this will result in duplication of theserecords in AXPLOG3.

Notice that you will not receive AX171F if the task that has the file open is DLOGor the report writer. In those cases, you will receive message AX171A instead ofAX171F.

WAITING TO RETRY OPEN OF AXPLOG1 - AXPL10After you respond R to message AX171F, the program issues message AX171G,waits 30 seconds, and then attempts to open the log file again. If this attempt fails,the program issues message AX171G again, waits 30 seconds, and attempts to openthe log file one more time. If this second attempt fails, the program repeats messageAX171F.

CANCELLED DUE TO OPERATOR REQUEST - AXPL10After you respond C to message AX171F, the program issues message AX171H andcancels.

AX171E

AX171F

AX171G

AX171H



AXPLOG1 SUCCESSFULLY OPENED - AXPL10After you respond R to message AX171F, if AXPL10 is eventually able to open theAXPLOG1 file, it issues message AX171I.

The purpose of AX171I is to inform the operator that the program is no longerwaiting to open AXPLOG1 and that it has proceeded with the rest of the log filepurge operation. No operator response is required.

INVALID OPERATION CODEThe control statement immediately preceding this message has an invalid operationcode. Refer to the BIM-ALERT Installation and Operations Guide for a descriptionof AXPL7 control statements.

INVALID OPERAND COLUMN nnThe control statement immediately preceding this message has an invalid operand.nn indicates the column position where the invalid operand is located. Refer to theBIM-ALERT Installation and Operations Guide for a description of AXPL7 controlstatements.

NOT ENOUGH STORAGE FOR SORT PROGRAMThis message indicates that less than 64K of partition storage (not GETVIS) isavailable for the SORT program. Increase the SIZE parameter in the EXECstatement. Usually SIZE=128K is the minimum needed for AXPL7. Refer to theBIM-ALERT Installation and Operations Guide for additional information.

NOT ENOUGH GETVIS SPACE FOR BUFFERSAXPL7 is unable to acquire GETVIS space for its I/O buffers. Adjust the SIZEparameter of the EXEC statement so that more GETVIS area is available. Note thatAXPL7's overall GETVIS requirements vary dramatically, depending on whether theVSAM file is being read. Refer to the BIM-ALERT Installation and OperationsGuide for additional information.

CONTROL STATEMENT CALLS FOR nnn INPUT TAPE FILESnnn indicates the number of tape files called for by the AXPL7 TAPEIN parameter.During the course of AXPL7's execution, the operator will be requested to mountnnn tapes.

AX171I

AX201

AX202

AX203

AX204

AX205



MOUNT INPUT FILE nnn. ENTER ANY RESPONSE WHEN READYAs AXPL7 becomes ready for each input tape file, it issues this message. nnn isincremented by one each time AX206 is issued. After the operator enters anyresponse, the program opens the file and begins to process it.

MOUNT OUTPUT TAPE. ENTER ANY RESPONSE WHEN READYAXPL7 issues this message before it opens the output tape file.

NO INPUT FILE SPECIFIEDNo tape input file was specified (TAPEIN nnn) and no VSAM input file wasspecified (VSAM=YES). At least one input file must be specified.

RECORDS IN/OUT DO NOT BALANCE.The number of records read does not match the number of records written to theoutput tape. This probably indicates an internal error. Contact BIM TechnicalSupport to resolve this problem.

INVALID EXEC PARMThe value specified for the JCL EXEC PARM is not valid. Correct the parameterand resubmit the job. For information about the EXEC PARM of the log file utilityAXPL10, refer to the BIM-ALERT Installation and Operations Guide.

AX206

AX207

AX208

AX209

AX210

ICCF Submittal Monitor Messages



BIM-ALERT/VSE TAS AREA NOT FOUNDAXPHI1 was unable to locate the TAS area for an ICCF user attempting to submit ajob. This is probably an internal AXPHI1 error. Contact BIM Technical Support forassistance.

BIM-ALERT/VSE AXPHI1 INITIALIZING, TRY SUBMIT AGAINAXPHI1 performs a brief initialization sequence the first time any ICCF user does aSUBMIT. During this brief interval, it cannot service a SUBMIT request from asecond user, and since it has no WAIT mechanism available to it, it must return tothe user without performing the SUBMIT. Retry the SUBMIT after waiting a fewseconds.

At all other times AXPHI1 is fully reentrant, and simultaneous SUBMIT requestsrequire no intervention from the user.

BIM-ALERT/VSE NO FREE WORK AREAAXPHI1 obtains a work area for each pseudo-partition, so this error should neveroccur. This is probably an internal error. Contact BIM Technical Support forassistance.

BIM-ALERT/VSE GETVIS FAILEDAXPHI1 acquires a small amount of system GETVIS at initialization. It alsoacquires about 2K of partition GETVIS (from the pseudo-partition) on a SUBMIT,which is released at the completion of the SUBMIT. Adjust the SIZE parameter ofthe EXEC statement so that more GETVIS area is available.

BIM-ALERT/VSE LOGICAL REC LTH INVALIDAXPHI1 encountered a record with zero length. This is probably an AXPHI1internal error. Contact BIM Technical Support for assistance.

BIM-ALERT/VSE BUFFER EXHAUSTEDThis is an AXPHI1 internal error. Contact BIM Technical Support for assistance.

AX250

AX251

AX252

AX253

AX254

AX255



SUBMIT HOOK ENABLE/DISABLE RC=xxTransactions AX7A and AX7B issue this message after attempting to enable(AX7A) or disable (AX7B) the BIM-ALERT submittal monitor for ICCF. The mostcommon values for RC and their meanings are as follows:

Value Meaning

00 The operation was successful.

20 BIM-ALERT/VSE is not currently active, and therefore the operation is notpossible. Wait until BIM-ALERT/VSE is active and execute the transaction again.

28 Program AXPHI1, the ICCF submittal monitor program, is not resident in theSVA. Load AXPHI1 into the SVA using the SET SDL JCL statement and thenexecute AX7A again.

2C ICCF is not active. Execute the transaction in the CICS partition where ICCF isrunning.

38 The submittal monitor was previously established, either by a previous executionof AX7A, or because BIM-ALERT/VSE was active at the time ICCF was started.

A few other return codes are defined. These are usually caused by a BIM-ALERTprogramming error. These AXPICCF return codes are listed on page 2-81.

AXPHI7D STARTING TRANSACTION AX7CAXPHI7D issues this message just before starting transaction AX7C in the PLTPI.

AX7C IS ACTIVETransaction AX7C issues this message once when it starts. Then it awakens every10 seconds to determine whether ICCF has activated. Normally, AX7C finds ICCFactive after its first 10-second wait interval, at which time it establishes the ICCFsubmittal monitor and terminates.

If you find transaction AX7C active long after it has issued AX256B, this isprobably due to one of the following:

• You normally start ICCF by issuing transaction I$ST, and that has not yet beendone. In this case, you should not purge transaction AX7C. It will terminateon its own, once ICCF has been activated.

• BIM-ALERT has not yet been activated. In this case, you should not purgetransaction AX7C. It will terminate on its own once BIM-ALERT is activated.

• Transaction AX7C was started inadvertently in a partition where you do notrun ICCF. In this case, it is safe to purge transaction AX7C.

AX256

AX256A

AX256B

Rules Assembly and Conversion Messages



ERROR(S) FOUND IN JCL PARAMETER * aaa=bbbbbbbb * IGNOREDAn error was found in the indicated PARM statement. aaa=bbbbbbbb indicates thestatement that was invalid. Correct the parameter and resubmit the job.

EXPECTED CONTINUATION NOT RECEIVEDThis message indicates one of the following:

• Continuation to another card is expected because the current statement endedwith a comma followed by a blank. However, on the next read, end-of-fileoccurred.

• The current verb is expected to have more parameters, but scanning wasprematurely terminated by a blank column.

Correct the statement and resubmit the job.

INVALID NUMERIC VALUEA decimal numeric field exceeded a value of 32767 or a hexadecimal field exceededa value of X'7FFF'. The remainder of the statement is ignored. Correct the statementand resubmit the job.

EXPECTED LEFT PARENTHESIS NOT RECEIVEDA parenthetical list was expected as the next value received in the current statement,but no left parenthesis was found. The remainder of the statement is ignored.Correct the statement and resubmit the job.

EXPECTED RIGHT PARENTHESIS NOT RECEIVEDThe next value received in the current statement is supposed to be in a parentheticallist, but the apparent end of the list was not followed with a right parenthesis. Theremainder of the statement is ignored. Correct the statement and resubmit the job.

INSUFFICIENT SPACE FOR GENERATING RULES TABLEGETVIS storage to build the rules table is acquired based upon the SIZ= parameterspecified for the rules assembly program AXPR1. (This is not the SIZE= parameterof the EXEC card.) This amount of storage proved to be insufficient to build thetable. The run is terminated. Increase the value of the SIZ= parameter, using eitherthe MAXIMUM TABLE SIZE field of the CALR Screen or, if you choose to build

AX301

AX302

AX303

AX304

AX305

AX306



your jobstream manually, the SIZ= parameter of the AXPR1 control statement. Thenresubmit the job. Note that changing this parameter on the CALR Screen is effectiveonly if you resubmit the entire CALR jobstream (both the CONVERT and theASSEMBLE steps). For further information about this parameter, refer to the BIM-ALERT/VSE Security Administrator's Guide.

NUMBER CONTAINS INVALID CHARACTERSA value in the current statement is required to be a decimal or hexadecimal value,but the value was found to contain invalid characters. The run is terminated.Correct the statement and resubmit the job.

BIM-ALERT/VSE NOT INITIALIZED, RUN=LOAD DISABLEDBIM-ALERT/VSE has not been started, and therefore you cannot load a rules table.If you are not attempting to do a load (RUN=LOAD), then this message may beconsidered informational. If you want to run with RUN=LOAD, start BIM-ALERT/VSE and then resubmit the job.

PARTITION GETVIS FAILEDInsufficient partition GETVIS is available to build the rules table. Either resubmitthe job with a smaller EXEC SIZE= value (in order to provide a larger GETVISarea) or adjust the value specified for AXPR1's SIZ= parameter (so that lessGETVIS is required).

JOBMASK MASK HAS UNACCEPTABLE VALUEA jobmask or security ID in the current JOBMASK statement is missing. Theremainder of the statement is ignored. Correct the JOBMASK statement so thatneither of these fields is null and resubmit the job.

DATASETNAME STRUCTURE IS UNACCEPTABLEEither the specified DS name string contains more than 44 characters, or a singlenode contains more than 8 characters, or a null string is specified as the dsname fieldin a DSNAME rule. The remainder of the current statement is ignored.

SYSTEM ACCESS CRITERIA *NOT* UPDATEDAXPR1 was unable to produce a rules table because of prior critical errors.Processing terminates without establishing a rules table. Correct the error andresubmit the job.

AX307

AX308

AX309

AX312

AX313

AX317



NO RULE STATEMENTS FOUNDThe RUN= parameter implied that a rules table was to be built, but no RULEstatements were present in the jobstream. Either change the RUN= parameter or addsome RULE statements, and then resubmit the job.

PREVIOUS aaaaaaaa bbbbbbbb NOT CHANGEDWhen multiple statements with the same membername are present, each must specifythe same overall action operand. If a subsequent statement specifies an actiondifferent from that of the first, the rules assembler issues message AX327, retains theaction specified for the first statement, and continues processing with the nextstatement.

‘aaaaaaaa’ indicates the resource type and ‘bbbbbbb’ indicates the action of thestatement that was in error.

To correct this error, remove the overall action operand from all but the firststatement. For more information, refer to the statement syntax descriptions ofdsaction (for DSNAME statements) and raction (for RESOURCE statements) in theBIM-ALERT/VSE Security Administrator's Guide.

This error should never occur if you maintain your rules using the online facility ofBIM-ALERT/VSE (ALXP). If you use ALXP and you receive this error message,contact BIM Technical Support for assistance in resolving the problem.

UNREACHABLE STATEMENTThe value in the current statement is the same as, or a subset of, the value in a priorstatement. The current statement will never be processed by the BIM-ALERT/VSErules processor during entry verification or access authorization checking. Correctthe statement and resubmit the job.

xxxxxxxx NOT VALIDThe current statement contains the invalid name xxxxxxxx. If the value is a characterstring, the valid characters will be used and the invalid ones ignored, and processingwill continue. Correct the value in error and resubmit the job.

VALUE EXCEEDS MAXIMUM LENGTHA value coded in the current statement contains more characters than specified in theappropriate RESOURCE statement. The program truncates the value to themaximum defined length and processing continues. Either correct the length valuein the RESOURCE statement or correct the resource value so that it does not exceed

AX320

AX327

AX328

AX329

AX330



the maximum length specified in the RESOURCE statement, and then resubmit thejob.

RESOURCE NAME STRUCTURE IS UNACCEPTABLEEither the resource class or resource name is missing, or the content of the resourcename is invalid.

For LIBRARY resources, the following special restrictions apply:

• Verify that the colon is present and that there is a DD name.

• If the format-1 label is an equal sign (=), the DD name must be UNKLIB?.

• If the DD name is UNKLIB?, the format-1 label must be an equal sign (=).

• Verify that no rule is already present that uses the same format-1 label but witha different DD name.

• Verify that no rule is already present that uses the same DD name, but with adifferent format-1 label.

PREVIOUS xxxxxxxx NOT CHANGEDThe current statement attempts to specify a value for xxxxxxxx, but a previousstatement has already assigned it a value. The value may be specified only once.Correct the statement and resubmit the job.

RESOURCE NOT PREVIOUSLY DEFINEDThe resource class of the current statement has not been previously defined. After aresource class is defined, a RESOURCE statement must be used to switch from oneassignment to another.

Add the proper RESOURCE statement or check whether the order of statements iscorrect. Then resubmit the job.

PARTIALLY UNREACHABLE STATEMENTThe source of a security ID was expressed as a range, and that range overlapped witha previously stated range or source device, with all other values of the statementsequal. The overlapped portion of the range is therefore unreachable.

Review the source ranges and correct the error. You may need to change severalstatements.

AX331

AX332

AX333

AX334



PASSWORD VALUE xxxxxxxx CONTAINS ILLEGAL CHARACTERSA password may contain only the uppercase letters A to Z, the numbers 0 to 9, andthe special characters asterisk (*), at-sign (@), dollar sign ($), and number sign (#).Correct the password and rerun the rules assembly and conversion jobs.

mmddyyyy IS AN INVALID DATEmm indicates the month and must be a value from 01 to 12. dd indicates the day ofthe month and must be consistent with the value specified for mm. yy indicates theyear. Values from 89 through 99 indicate years 1989 through 1999. Values from 00through 41 indicate years 2000 through 2041. Values from 42 through 88 areinvalid. A value of 000000 indicates that the GROUP rule never expires. Refer tothe BIM-ALERT/VSE Security Administrator's Guide for more information about theGROUP rule.

UNKNOWN OPTION - BYPASSEDThe OPTION statement contains an invalid option value. Correct the statement andresubmit the job.

INVALID FIELD IDThe USER statement permits a limited set of values for the idname and bldnamefields. The name used was not one of those values. Correct the name of the jobcardfield to be accessed and resubmit the job.

ERROR IN THE FORMAT OF THE USER STATEMENTEither required operands of the USER statement were omitted, parentheses wereused incorrectly, or continuation was incorrectly coded. Check for the omission ofrequired fields or for misplaced or missing parentheses. If additional information isexpected, check for no ending comma or no continuation card. Correct the statementand resubmit the job.

POSITION-LENGTH COMBINATION EXCEEDS FIELD BOUNDARIESThe field addressed by the USER statement has a set length, which was exceeded bythe specified operand list. Correct the statement by shortening the list and resubmitthe job.

GETVIS FAILED, INSUFFICIENT SVA FOR RULES TABLEThere is not enough contiguous system GETVIS storage to hold the new rules table.It will not be possible to load the new table until the next IPL.

AX335

AX337

AX338

AX339

AX340

AX341

AX346



If this error occurs during BIM-ALERT/VSE startup at IPL, it will probably benecessary to allocate additional system GETVIS area before you will be able to bringup BIM-ALERT/VSE. This is done by increasing the GETVIS parameter of the SVAcontrol statement in your ASI IPL procedure.

BACKLEVEL RULES TABLEThe rules table was assembled using a version of BIM-ALERT/VSE prior to version5.0 and is incompatible with BIM-ALERT/VSE version 5.0. Reassemble the rulestable with BIM-ALERT/VSE version 5.0.

TABLE HAS INCORRECT SECURITY ID (SID)The specified security ID (SID) value does not match that of the phase loaded fromthe library. The OBJ and SID values are both specified by the security administratorwhen a rules table is assembled. Verify that the OBJ value specified is the name ofthe phase you actually want. Verify that the SID value is coded correctly. If both ofthese values are correct, check for duplicate phases in two libraries in the SEARCHchain.

During an activate run, the SID value is specified in a control statement, either fromSYSIPT or from the control file. During a modify run, the SID value is entered bythe console operator in response to message AX371.

TABLE LTH OR PHASE NAME MISMATCHThe rules assembler program stores the phase name and length inside the phaseitself. AX350 means that one or the other of these does not match the correspondingvalues in the directory entry. The phase may have been renamed or the member mayhave been corrupted in the library.

RULES TABLE REQUIRES x,xxx,xxx BYTESThis message shows the size of the rules table. This is the amount of systemGETVIS area required to load the table.

PREVIOUS STATEMENT IGNOREDThe statement is being ignored because of syntax errors.

SKIPPING TO NEXT STATEMENTDue to an error in the statement, syntax scanning will begin on a new statementboundary.

AX347

AX349

AX350

AX351

AX352

AX353



STATEMENT IGNORED MESSAGE COUNTS, WRONG VERB- aaaaaaa,STMT CONTINUED - bbbbbbbaaaaaaa is the number of statements ignored due to an invalid verb. bbbbbbb is thenumber of statements ignored scanning for the end of a statement.

SYSTEM ACCESS CRITERIA *UPDATED*AXPR1 has invoked the operating system linkage editor ($LNKEDT) in order tocatalog the rules table that was just assembled into the library.

TABLE IS NOT LINKED BECAUSE RUN=DEBUG USEDThe purpose of RUN=DEBUG is for syntax scan only. This message indicates thatthe table was not placed in the library because that run option was specified.

VERB IS INVALID OR OUT OF SEQUENCE * xxxxxxxxxxxxxxx *The verb xxx...xxx is invalid or is not in the specific order required. Refer to theBIM-ALERT/VSE Security Administrator's Guide for information about the requiredsequence.

TABLE IS NOT LINKED BECAUSE OF CRITICAL ERRORSThe table was not placed in the library because of previously reported errors.

* xxxxxxxx * VERB IS NOT USEDNo statement of type xxxxxxxx was encountered in the run. This is an informationalmessage only.

TABLE PHASE xxxxxxxx NOT FOUND IN LIBRARYThe OBJ= value xxxxxxxx was used to load the rules table, but no phase with thatname was found. Verify that the OBJ= value is correct. Verify that the librarywhere the phase resides is in the SEARCH chain for the partition where the job wasrun.

PARAMETER ERROR xxx= IGNOREDThe console operator entered an erroneous xxx= parameter. The parameter isignored and the program prompts for another parameter. Determine the correctformat for the parameter and reenter it.

AX355

AX356

AX358

AX359

AX360

AX361

AX363

AX365



COMRG LINK OPTION BIT NOT ON - LINK EDIT WON'T WORKWhen RUN=SAVE is specified, the rules assembly program invokes the linkageeditor to catalog the rules table into a library. This requires that // OPTION CATALbe specified. Notice that the // OPTION CATAL must be positioned in thejobstream after any DLBL for IJSYSLN.

ENTER BIM-ALERT/VSE RUN PARAMETERS OR 'END'When the AXPR1 program is executed from the operator console or whenCON=YES is specified to permit console override, the program prompts for RUNparameters by issuing this message. Enter a desired RUN parameter. The programwill reissue AX372, prompting you for additional parameters. When you haveentered all the parameters, then enter END.

MAKE ADDITIONAL CHANGES OR ENTER E.O.BThis message is displayed after you enter END in response to AX372. At this point,you can enter additional changes to the RUN parameters.

Messages AX403 through AX410 are issued by program AXPU002. These messagescannot occur if you use CALR to submit the rules conversion and assembly jobbecause CALR validates your parameters before submitting the job.

If you do not use CALR, you must validate the parameters yourself before yousubmit the job. For information about these parameters, refer to the BIM-ALERT/VSE Security Administrator's Guide.

NO TABLE PARAMETER SPECIFIED - JOB TERMINATEDInclude a TABLE=nn parameter in the jobstream and rerun the job. nn indicates thenumber of the table that you want to convert and assemble.

TABLE NUMBER xx DOES NOT EXISTThe table number you specified in the NUMBER field of the CALR panel does notexist in the ALERTXP security file. Perform the CALR request again with a validtable number.

INVALID KEYWORD PARAMETERYour AXPU002 job contains a control statement with a keyword that is not RUN=,SIZ=, LIN=, or OBJ=. Correct the invalid keyword and rerun the job.

AX366

AX372

AX373

About MessagesAX403 ThroughAX410

AX403

AX403A

AX404



INVALID PARAMETER - STATEMENT IGNOREDA control statement in the AXPU002 jobstep contains a keyword with an invalidparameter. The message is preceded by an image of the control statement in error.Correct the invalid parameter and rerun the job.

SIZ= PARAMETER INVALID - DEFAULT 20K USEDThe SIZ= parameter contains an invalid value. AXPU002 substitutes SIZ=20K.

LIN= PARAMETER INVALID - DEFAULT 88 USEDThe LIN= parameter contains an invalid value. AXPU002 substitutes LIN=88.

SERIOUS ERRORS DETECTED - JOB TERMINATEDOne of the following errors occurred: AX403, AX404, AX405, AX410, AX411,AX412, AX413, AX415, or AX807. AXPU002 terminated with a return code of 12.

DEFAULT PARAMETER ADDED TO JOB STREAMIf any of the following keyword parameters is missing, AXPU002 substitutes thefollowing default value:

Keyword Default Value

RUN SAVE

SIZ 20K

LIN 88

This is an informational message. No action is required.

NO OBJ= PARAMETER PRESENT - JOB TERMINATEDThe OBJ= parameter specifies the name of the library member to be cataloged duringthe AXPR1 rules assembly step. It is a required parameter. Rerun the job withOBJ= specified.

ERROR OPENING ALERTXP FILE R15=aa, RC=cccWhen AXPU002 tried to open the ALERTXP file, VSAM returned an error code.Register 15 contains the decimal value aa. ccc is the decimal value of the returncode. For an explanation of this code, refer to the section "Error Codes from OPEN"in the IBM publication VSE/VSAM Messages and Codes.

AX405

AX406

AX407

AX408

AX409

AX410

AX411



ERROR ISSUING POINT MACRO - R15=aa, RC=cccWhen AXPU002 tried to perform a VSAM POINT operation on the ALERTXP file,VSAM returned an error code. Register 15 contains the decimal value aa. ccc is thedecimal value of the return code. For an explanation of this code, refer to the section"Error Codes from Request Macros" in the IBM publication VSE/VSAM Messagesand Codes.

ERROR ACCESSING xxxxxxxx FILE - R15=aa, RC=cccWhen AXPU002 tried to perform a GET operation on the ALERTXP file, VSAMreturned an error code. ‘xxxxxxxx’ is the name of the file being accessed. Register15 contains the decimal value aa. ccc is the decimal value of the return code. For anexplanation of this code, refer to the section "Error Codes from Request Macros" inthe IBM publication VSE/VSAM Messages and Codes.

NO xxxxxxxx RECORDS IN TABLE nnThe rules conversion program, AXPU002, found no records of type xxxxxxxx in thetable being converted, table nn.

Possible values for xxxxxxxx are as follows:

Value Description

PROFILE User profile rules

JOBMASK JOBMASK rules

SECID SECID rules

TAPEDS Tape dataset rules

DASDDS DASD dataset rules

LIBMEM Library member rules

SUBLIB Sublibrary member rules

RESOURCE OTHER rules, such as DITTO, ENVRES, or LIBRARY

This message is for information only. No corrective action is required.

GETVIS ERROR - RETURN CODE = ccc IN DECIMALWhen AXPU002 issued a GETVIS request, VSE returned error code ccc. Forexplanations of the GETVIS return codes, refer to page 2-84.

The most common return code is 012 (X'0C'), which means that insufficient storageis available in the GETVIS area of the partition. Verify that the program was

AX412

AX413

AX414

AX415



executed with SIZE=AXPU002. If you execute it with SIZE=AXPU002 and stillreceive AX415, run the jobstream in a partition with a larger GETVIS area.

PASSWORD HAS INVALID CHARACTERSThe statement displayed before message AX416 has a password parameter withinvalid characters. A password may contain only the uppercase letters A to Z, thenumbers 0 to 9, and the special characters asterisk (*), at-sign (@), dollar sign ($),and number sign (#). The run continues, but the password value is not encrypted.This results in an incorrect value in the associated rule and can lead to an AXPR1syntax error. To correct the problem, use ALXP to update the rule with the invalidpassword and then rerun the conversion jobstream.

AX416

Messages Relating to CA-VOLLIE, DITTO, and Other Programs



FOLLBGP ERROR M=mname.mtype S=lib.sublib MSG=xxxxxxxxLibrarian access module FOLLBGP detected an error. mname.mtype is the requestedmember name and member type. lib.sublib is the requested library name andsublibrary name. xxxxxxxx is the message text returned by FOLLBGP. The textdescribes the specific error condition. The following are some of the possible valuesfor xxxxxxxx and their meanings:

Value Meaning

GETVIS FAILED FOLLBGP's request for GETVIS storage failed. Adjust the EXECSIZE parameter to provide a larger GETVIS area, or run the job in apartition with a larger GETVIS area.

UNKNOWNLIBRARY

Either the requested library is invalid, or no DLBL was found for thespecified library name, or the requested sublibrary is not a validsublibrary in the specified library.

INVALIDMEMBER TYPE

Members of type DUMP or PHASE cannot be processed byFOLLBGP.

MEMBER NOTFOUND IN LIB

The requested member does not reside in the specified sublibrary.

If you specified the parameter ACTION CONTINUE, AXPU4continues processing the other input commands and sets a return codeof 4.

Otherwise, AXPU4 terminates with a return code of 8 withoutprocessing any further commands. Either rerun the request from thecorrect sublibrary or correct the spelling of the member name ormember type.

Other values are possible for xxxxxxxx. These usually indicate either a programmingerror or library corruption. Call BIM Technical Support for assistance in resolvingthe problem.

AX6C IS ACTIVE, SUBMIT SUPPRESSED.When AX6C is active, CA-VOLLIE submit activity is suspended. Wait a moment,and then re-issue the submit request.

This message is displayed both on the system operator console and on the terminal ofthe CICS operator who requested the submit.

AX417

AX418



AXPHJ6B LOADED.Either BIM-ALERT's CA-VOLLIE submit exit program (AXPHJ6) or transactionAX6C (program AXPHJ6G) has loaded the local CA-VOLLIE submit exit program(AXPHJ6B).

This message is issued on the system operator console (by AXPHJ6 and AX6C) andat the CICS operator's terminal (by AX6C only). It is for information only; nocorrective action is required.

WAITING FOR SUBMIT TO COMPLETEThe AX6C/AXPHJ6 enqueuing record indicates that a CA-VOLLIE submitoperation is in progress, and AX6C is waiting for it to complete. If the submitoperation completes within 30 seconds, AX6C executes successfully and thenterminates with message AX421.

If the submit operation is still not complete after 30 seconds, AX6C issues messageAX422 and terminates without reloading AXPHJ6B. In this case, reissue the AX6Crequest after the submit operation is complete. If the error persists, refer to the BIM-ALERT/VSE Security Administrator's Guide for information about other correctivemeasures you can take.

AX6C PROCESSING SUCCESSFUL.AX6C completed successfully, and program AXPHJ6B has been reloaded. Thismessage is for information only; no corrective action is required.

AX6C PROCESSING FAILED.AX6C terminated without reloading AXPHJ6B. Another message describing thereason for the failure will accompany message AX422. Perform the correctiveaction indicated by that message and then execute transaction AX6C again.

CONCURRENT AX6C EXECUTIONS NOT ALLOWED.The AX6C/AXPHJ6 enqueuing record indicates that another execution of AX6C isin progress. Wait a moment and then execute AX6C again. If the error persists,refer to the BIM-ALERT/VSE Security Administrator's Guide for information aboutother corrective measures you can take.

INCORRECT PLACEMENT OF CONTROL STATEMENTSControl statements must be presented to AXPU4 in the following prescribedsequence:

AX419

AX420

AX421

AX422

AX423

AX424



• ACTION statement. This must precede any other statements. Only oneACTION statement is permitted.

• USER statement. This must precede the first ACCESS statement. Only oneUSER statement is permitted.

• ACCESS statements. These must precede the first LOAD statement. MultipleACCESS statements are permitted.

• LOAD statements. An ACCESS statement must precede any LOADstatements. Multiple LOAD statements can follow a single ACCESSstatement.

NO SUBMITLM RULES DEFINEDNo rules are defined for the SUBMITLM resource class, and therefore AXPU4cannot be executed by anyone. The program terminates without submitting any job.

BIM-ALERT/VSE IS NOT ACTIVE, JOB SUBMITTED WITH USERID NO-SEC. PGM=ppppppppBIM-ALERT/VSE is not active, so program AXPU4 is unable to validate thesubmittor's authorization level. AXPU4 submits the job with a user ID of NO-SECinstead of the one specified in the USER statement.

NOT ENOUGH GETVIS FOR DITTO AUTHORIZATIONWith BIM-ALERT/VSE's DITTO security in place, DITTO executions require about4k of additional GETVIS. Execute the DITTO request again, decreasing the EXECSIZE parameter by 4k. (Decreasing the SIZE parameter increases the amount ofGETVIS.)

UNABLE TO PERFORM DITTO AUTHORIZATION - REASON =nnAn internal check in program AXPHDT1 failed. nn is the specific check that failed.Contact BIM Technical Support for assistance in resolving this problem.

TAPE OPEN CHANGED ASSIGNMENT TO CUU. OK?Your DITTO tape command requested a specific cuu address for the tape volume,but the OPEN changed the cuu to a different one. If this is acceptable, mount thetape volume on the indicated drive and respond Y to AX452. If this cuu is notacceptable, respond N (or anything other than Y) and the job will be canceled.

AX425

AX426

AX450

AX451

AX452



TAPE ASSIGN TO CUU. OK?DITTO allows you to specify a tape device address as SYSnnn or cuu. You canspecify SYSANY for SYSnnn or ANY or for cuu to indicate that you want the tapeaddress assigned dynamically at execution time.

Message AX453 tells you the tape address that BIM-ALERT has assigned. RespondY if the address is acceptable. Respond something other than Y if the address is notacceptable.

If you specified ANY and BIM-ALERT cannot find a free tape address, BIM-ALERT issues message AX454 and cancels the job.

NO FREE TAPESee the description of message AX453.

UNKNOWN DITTO COMMAND xxxThe DITTO command that you entered is acceptable to DITTO, but it is unknown toBIM-ALERT. BIM-ALERT is unable to assign the command to a BIM-ALERTcategory and therefore cannot perform a proper security check. The job is canceled.

This probably indicates that you are using a version of DITTO that BIM-ALERT isnot designed to handle. Contact BIM Technical Support for assistance in resolvingthis problem.

AXPU2 NO ACTION TAKEN - SECURITY NOT ACTIVE.When VSE has been IPLed without SEC=YES, AXPU2 will not insert an IDstatement.

AXPU2 CANNOT PROCESS - SYSPCH NOT ASSIGNED.AXPU2 uses the SYSPCH logical unit for its output. If SYSPCH is not assigned, itdoes not attempt to punch anything.

Rerun the jobstream after assigning SYSPCH to an appropriate device.

AXPU2 NO ACTION TAKEN - SYSPCH NOT POWER DEVICE.If the SYSPCH device is not controlled by VSE/POWER, AXPU2 will not insert anID statement.

Rerun the jobstream after assigning SYSPCH to a device that is controlled byVSE/POWER.

AX453

AX454

AX455

AX456

AX457

AX458



AXPU2 NO ACTION TAKEN - NOT PUN DISP=I.If SYSPCH is not set up for PUN DISP=I, AXPU2 will not insert an ID statement.

Rerun the jobstream with the "* $$ PUN DISP=I" JECL control statement.

AXPU2 NO ACTION TAKEN - CANNOT LOCATE POWER DEVICE LIST.In order to determine whether SYSPCH is assigned to a POWER-controlled deviceand whether PUN DISP=I is in force, AXPU2 must locate a table insideVSE/POWER. If the program is unable to locate the table, it will not insert an IDstatement.

If this error message occurs, you are probably running a version of VSE/POWERthat AXPU2 is not designed to handle. Contact BIM Technical Support forassistance.

AXPU2 CANNOT PROCESS - UNABLE TO LOCATE/LOAD PHASEAXPU2A.AXPU2 is unable to load phase AXPU2A into the SVA. This indicates one of thefollowing conditions:

• The SVA is full.

• The sublibrary where AXPU2A resides is not accessible to the partition whereAXPU2 is executing.

Ensure that the sublibrary where AXPU2A resides is in the LIBDEF PHASE searchchain.

AXPU2 NO ACTION TAKEN - NODE.USERID NOT IN PDEST LIST.A DEST or PDEST parameter is present and the specified NODE.USERID is notlisted in phase AXPU2B. AXPU2 will not insert an ID statement.

If you want the jobstream to have an ID inserted, add the NODE.USERID to phaseAXPU2B. Refer to the BIM-ALERT Installation and Operations Guide forinstructions.

AX459

AX460

AX461

AX462

IPL Exit Messages


IPL Exit Messages

BIM-ALERT/VSE IPL EXIT ACTIVEThis message announces the presence of BIM-ALERT's IPL exit program,$SYSOPEN. No operator response is required.

BIM-ALERT/VSE IPL EXIT - PROCESSING COMPLETEDSUCCESSFULLYBIM-ALERT's IPL exit program, $SYSOPEN, has completed successfully. Nooperator intervention is required.

BIM-ALERT/VSE IPL EXIT - CONTROL PASSED TO PROGRAM xxxxxxxxThe BIM-ALERT installation process renames any existing $SYSOPEN phase toAXP$OPEN, provided no such phase already exists. When AXPIPLX runs as$SYSOPEN, it passes control to phase AXP$OPEN. This message indicates thatAXPIPLX has passed control to another program.

BIM-ALERT/VSE IPL EXIT - xxxxxxxx BYPASSED, IS AXPIPLXThe phase named AXP$OPEN is another copy of AXPIPLX. AXPIPLX has notpassed control to the other program but has instead returned control to the operatingsystem. To avoid this message, delete the duplicate copy of AXPIPLX fromIJSYSRS.SYSLIB.

BIM-ALERT/VSE IPL EXIT - IPL'D WITH SEC=NOBIM-ALERT's IPL exit is present, but the IPL specifies SEC=NO. The exit takes noaction. It will not be possible to activate BIM-ALERT.

BIM-ALERT/VSE IPL EXIT - ENTER PASSWORD FOR SEC=NOThe system is being IPLed with SEC=NO and the control file indicates that apassword is required. Type the password for IPLing with SEC=NO and pressENTER.

BIM-ALERT/VSE IPL EXIT - PASSWORD IS INCORRECTThe password you entered is incorrect. Type the password again and press ENTER.

AX495A

AX495B

AX495C

AX495D

AX496

AX496A

AX496B

IPL Exit Messages


BIM-ALERT/VSE IPL EXIT - ENTER PASSWORD FOR IPLThe control file indicates that a password is required for to IPL the system. Type theIPL password and press ENTER.

BIM-ALERT/VSE IPL EXIT - ALREADY PRESENT IN THE SVAAXPIPLX has received control and found a copy of AXPIPLX already present in theSVA. This means that AXPIPLX has been given control twice. This can happen ifAXPIPLX has been renamed to both $SYSOPEN and AXP$OPEN, or if another$SYSOPEN phase passes control to AXPIPLX.

After issuing this message, AXPIPLX passes control to the next $SYSOPEN phase.

AX496C

AX497

Emergency Override Messages


Emergency Override Messages

OVERRIDE JOB ACTIVEThe operator's response to message AX499 confirmed that the job is a BIM-ALERT/VSE override job.

OVERRIDE JOB NOT ACTIVEThe operator's response to message AX499 indicated that the job is not a BIM-ALERT/VSE override job.

IS THIS AN OVERRIDE JOB?Normally, this message is issued when the security administrator submits a BIM-ALERT/VSE override job. The job pauses after AX499 and waits for a responsefrom the console operator. Consult with the security administrator to determine thecorrect response to this message. If you are unable to determine the correctresponse, enter a null response to cause the job to proceed as a normal job instead ofas an override job.

AX498A

AX498B

AX499

Online Error Messages



The online error message numbers are directly related to the name of the programthat produced the message. Messages AX502 to AX519 are produced by programAXP500, messages AX520 to AX539 are produced by program AXP520, and so on.The only exceptions are AX500 and AX501, which are produced by the drivermodule AXP10000.

Additional online error messages are described beginning on page 2-73.

NO PROCESSING FUNCTION REQUESTED ... REENTEREnter an X next to the desired function before pressing the ENTER key.

XXXX IS NOT A VALID SECURITY SYSTEM TRANSACTIONAn invalid subfunction transaction ID was entered. Press clear and reenter the ID.

ERRORS DETECTED - CORRECT AND REENTERThe highlighted fields on the screen did not pass the validation edits. Correct andreenter them.

USER INFORMATION ADDED TO FILEThe USER rule has passed all edits and has successfully been added to the securityfile.

INVALID FUNCTION SPECIFIED - CORRECT AND REENTERAn invalid or improper response has been entered. Correct and reenter yourresponse.

NO USER STATEMENTS FOUND IN TABLE nnThere are no USER statements in the file in the table requested. Correct and reenterthe table number.

USER INFORMATION SUCCESSFULLY UPDATEDThe requested updates to a user rule have been successfully completed.

Introduction

AX500

AX501

AX502

AX503

AX510

AX514

AX515



ERROR WRITING TO TEMP STORAGE QUEUEAn error occurred during an attempt to write a record to temporary storage. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

ERROR ACCESSING TEMP STORAGE QUEUEAn error occurred when the system tried to read a record from temporary storage.Run a trace to determine the temporary storage return code and refer to page 5-5 forits meaning.

ERROR RELEASING TEMP STORAGE QUEUEAn error occurred during an attempt to release the temporary storage used. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

GETVIS ERROR - RETURN CODE IS cc IN DECIMALAn error resulted from a response to a request for table storage. Refer to the list ofGETVIS return codes on page 2-84 to determine the source of the problem.

ERRORS DETECTED - CORRECT AND REENTERThe highlighted fields on the screen did not pass the validation edits. Correct andreenter the information.

JOBMASK INFORMATION ADDED TO FILEThe jobmask rule has passed all edits and has successfully been added to the securityfile.

INVALID FUNCTION SPECIFIED - CORRECT AND REENTERAn invalid or improper response to a prompt has been entered. Correct and reenteryour response.

NO JOBMASK STATEMENTS FOUND IN TABLE nnThere are no JOBMASK statements in the file in the table requested. Correct andreenter the table number.

AX516

AX517

AX518

AX519

AX522

AX523

AX530

AX534



JOBMASK INFORMATION SUCCESSFULLY UPDATEDThe requested updates to a jobmask rule have been successfully completed.

ERROR WRITING TO TEMP STORAGE QUEUEAn error occurred during an attempt to write a record to temporary storage. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

ERROR ACCESSING TEMP STORAGE QUEUEAn error occurred during an attempt to read a record from temporary storage. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.


GETVIS ERROR - RETURN CODE IS cc IN DECIMALAn error occurred during a request for table storage. Refer to the list of GETVISreturn codes on page 2-84 to determine the source of the problem.


SECID INFORMATION ADDED TO FILEThe security ID rule has passed all edits and has successfully been added to thesecurity file.


AX535

AX536

AX537

AX538

AX539

AX542

AX543

AX550



NO SECID STATEMENTS FOUND IN TABLE nnThere are no security ID statements in the file in the table requested. Correct andreenter the table number.

SECID INFORMATION SUCCESSFULLY UPDATEDThe requested updates to a security ID rule have been successfully completed.

ERROR WRITING TO TEMP STORAGE QUEAn error occurred during an attempt to write a record to temporary storage. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

ERROR ACCESSING TEMP STORAGE QUEUEAn error occurred during an attempt to read a record from temporary storage. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.


GETVIS ERROR - RETURN CODE IS cc IN DECIMALAn error has been returned in response to a request for table storage. Refer to the listof GETVIS return codes on page 2-84 to determine the source of the problem.



AX554

AX555

AX556

AX557

AX558

AX559

AX560

AX561



NO SECID INFORMATION - CORRECT AND REENTERYou tried to add DATASET records with no security ID information. Add therequired information and reenter.

ERROR X'cc' DURING GETNEXT PROCESSINGAn error occurred during a browse of the file. Refer to page 5-3 to determine themeaning of the file access return code X'cc'.

ERROR X'cc' DURING GETAREA PROCESSING FOR SECID RECORDEither the file is full or it is closed. Refer to page 5-3 to determine the meaning ofthe file access return code X'cc'.

ERROR X'cc' ADDING SECID GROUP RECORDAn error occurred during an attempt to add a new security ID group record to thefile. Refer to page 5-3 to determine the meaning of the file access return code X'cc'.

ERROR X'cc'. TYPE=tttttt. PGM=pppppp.CICS returned a file access error on the online security file (ALERTXP). Refer topage 5-3 to determine the meaning of the file access return code X'cc'.

ERROR X'cc' ON CONTROL RECORD. TYPE=tttttt. PGM=pppppp.CICS returned a file access error when the program tried to access a control record inthe online security file (ALERTXP). Refer to page 5-3 to determine the meaning ofthe file access return code X'cc'.

NO RECORDS FOUND TO UPDATE/DISPLAYThe program did not find the specific record you requested to update or display.Check the spelling of the ruleset name, make corrections, and press ENTER to trythe request again. If you use browse (PF1) to access records to update or display, theprogram displays this message when it reaches the end of the records that meet yourbrowse criteria. In this case the message is for information only and requires nocorrective action.

ERROR X'cc' UPDATING SECID GROUP CONTROL RECORDAn error occurred while attempting to rewrite a security ID group control record tothe file. Refer to page 5-3 to determine the meaning of the file access return code.

AX562

AX568

AX569

AX570

AX571

AX572

AX574

AX577



DATASET NAME RECORDS SUCCESSFULLY UPDATEDThe DATASET rule has passed all edits and has successfully been updated.

DATASET NAME RECORDS SUCCESSFULLY ADDEDThe DATASET rule has passed all edits and has successfully been added to thesecurity file.

ERROR ACCESSING TEMP STORAGE RECORDAn error has been returned in response to a request for a temporary storage record.Run a trace to determine the temporary storage return code and refer to page 5-5 forits meaning.

GETVIS ERROR - RETURN CODE IS cc IN DECIMALAn error has been returned in response to a request for table storage. Refer to the listof GETVIS return codes on page 2-84 to determine the source of the problem.

TABLE OVERFLOW - CONTACT BIM TECHNICAL SUPPORTThe storage requested for work space on a display or update operation is insufficient.Contact BIM Technical Support for a patch that allows you to acquire more storage.

GETVIS ERROR - RETURN CODE IS cc IN DECIMALAn error has been returned in response to a request for table storage. Refer either topage 5-6 or to the IBM publication VSE Macro Reference Guide to determine themeaning of the return code.

ERROR WRITING TO TEMP STORAGE QUEUEAn error was returned from an attempt to write a record to temporary storage. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

ERROR ACCESSING TEMP STORAGE QUEUEAn error was returned from an attempt to read a record from temporary storage. Runa trace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

AX578

AX579

AX579A

AX579B

AX579C

AX620

AX621

AX622



ERROR RELEASING TEMP STORAGE QUEUEAn error was returned from an attempt to release the temporary storage used. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

USER SEQUENCE MOVE PENDINGA MOVE command has been issued on one panel and you have used PF8 or PF7 topage. This message is a reminder that an action is still pending.

NO PROCESSING FUNCTION SPECIFIED ... REENTEREnter an X next to the desired function before pressing the ENTER key.

INVALID PROCESSING FUNCTION - CORRECT AND REENTERAn invalid or improper response to a prompt has been entered. Correct and reenteryour response.

ERROR X'cc' DURING GETNEXT PROCESSINGAn error has been returned during a browse of the file. Refer to page 5-3 todetermine the meaning of the file access return code X'cc'.

NO USER STATEMENTS FOUND IN TABLE nnThere are no USER statements in the file in the table requested. Correct and reenterthe table number.

USER SEQUENCE SUCCESSFULLY UPDATEDUpdate processing has successfully completed.

GETVIS ERROR - RETURN CODE IS cc IN DECIMALAn error has been returned in response to a request for table storage. Refer either topage 5-6 or to the IBM publication VSE Macro Reference Guide to determine themeaning of the return code.

AX623

AX625

AX626

AX627

AX628

AX634

AX635

AX640



ERROR WRITING TO TEMP STORAGE QUEUEAn error was returned from an attempt to write a record to temporary storage. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

ERROR ACCESSING TEMP STORAGE QUEUEAn error was returned from an attempt to read a record from temporary storage. Runa trace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

ERROR RELEASING TEMP STORAGE QUEUEAn error was returned from an attempt to release the temporary storage used. Run atrace to determine the temporary storage return code and refer to page 5-5 for itsmeaning.

JOBMASK SEQUENCE MOVE PENDINGA move command has been issued on one panel and you have used PF8 or PF7 topage. This message is a reminder that an action is still pending.

NO PROCESSING FUNCTION SPECIFIED ... REENTEREnter an X next to the desired function before pressing the ENTER key.

INVALID PROCESSING FUNCTION - CORRECT AND REENTERAn invalid or improper response to a prompt has been entered. Enter a validresponse.

ERROR X'cc' DURING GETNEXT PROCESSINGAn error has been returned during a browse of the file. Refer to page 5-3 todetermine the meaning of the file access return code X'cc'.

NO JOBMASK TABLE FOUND IN TABLE xxThere are no JOBMASK statements in the file in table xx. Enter a correct tablenumber.

AX641

AX642

AX643

AX645

AX646

AX647

AX648

AX654



JOBMASK SEQUENCE SUCCESSFULLY UPDATEDUpdate processing has successfully completed.

ENTER INPUT JOBSTREAM INFORMATION OR ENTER TO SUBMIT JOBIf the information displayed is correct, press ENTER to submit the job toVSE/POWER. If not, make the necessary changes and press ENTER.

ERRORS DETECTED - CORRECT AND REENTERThe information supplied has not passed all edit tests. Correct the highlighted fieldsand press ENTER.

JOB SUCCESSFULLY PLACED IN READER QUEUEThe information supplied has been successfully placed into the VSE/POWER readerqueue.

CDLOAD FAILURE - PHASE AXPU003 NOT FOUNDThe phase that builds the jobstream could not be located in the core image library.Check the library search chain to ensure that the proper library is there.

REQUIRED KEYWORD OPERAND xxxxxxxxxx IS NOT PRESENTThe indicated keyword operand xxxxxxxxxx is required for the type of operationrequested, but it is not specified in the control statement. The program is unable toperform the requested operation without the information that would be supplied bythe keyword operand.

mmmm ERROR rc.fc FUNC=xxxxxxx PGM=AXP680mmmm is either PSPL or XPCC, as follows:

• If mmmm is PSPL, the value for xxxxxxx is PUTRDR, which indicates that thefailure occurred while sending the data buffer that contains the jobstream itself.rc is the PXPRETCD value and fc is the PXPFBKCD value.

• If mmmm is XPCC, then xxxxxxx shows the specific XPCC-type function thatfailed. rc is the IJBXRETC value and fc is the IJBXREAS value.

AX655

AX680

AX681

AX682

AX683

AX684

AX685



ATTACH ERROR - RC=ccc IN DECIMALThe ATTACH has returned an error. The probable cause is that ICCF has a pseudo-partition active. Try again later. If this does not solve the problem, contact BIMTechnical Support for assistance.

ERROR X'cc' READING/RELEASING JOB ENTRY RECORDAn error occurred while attempting to read the record containing the job entryinformation. The probable cause is that the file is closed. Refer to page 5-3 for themeaning of the file access return code X'cc'.

AX686

AX687

Messages from Program AXPU004



ERROR ON ALERTXP aaaaa RC=bb FDBK=ccAn error resulted from an attempted operation on the ALERTXP file (the BIM-ALERT/VSE rules file). After issuing the message, the program produces a dump ofthe partition.

aaaaa is the type of operation (OPEN, GET, PUT, and so on). bb is the return codevalue from register 15. cc is the return code. Refer to the descriptions of VSAM errorcodes on page 5-7 for the meaning of code cc. If the code is not listed there, refer tothe IBM publication VSE/VSAM Messages and Codes for a complete list of thesecodes.

If you are still unable to resolve the problem, call BIM Technical Support forassistance. Have the partition dump available when you call.

TABLE xx ALREADY EXISTSThe requested operation (MODEL-TABLE, COMBINE, or DESCRIBE) is intendedto create a new table, but the specified new table ID already exists. Either changethe control statement to specify a NEWTABLE parameter that does not alreadyexist, or remove the existing table from the file before you execute the MODEL-TABLE, COMBINE, or DESCRIBE.

In the case of DESCRIBE, if you intended to add a description to an existing table,use the OLDTABLE parameter instead of the NEWTABLE parameter in yourcontrol statement.

TABLE xx NOT FOUNDThe requested operation refers to a table ID that is not present in the ALERTXP file.Change the control statement so that it specifies the correct table ID and resubmit thejob.

SECID xxxxxxxx NOT REFERENCED IN ANY RESOURCE RECORDThe SECID operand of an AXPU004 control statement indicates which resourceauthorization records you want AXPU004 to erase, copy, or modify (rename). Whenyou specify a SECID value that is not referred to by any resource authorizationrecord in the file, the program issues message AX691 and terminates. Examine theOLDSECID, NEWSECID, or SECID operand and change it to specify a value that isreferred to in the file.

Note that the SECID operand you specify for an AXPU004 control statement has nodirect relationship to a SECID rule. (SECID rules are those defined on a user profile

AX688

AX689

AX690

AX691



or through the Extended Functions of ALXP.) Rather, these SECID operands referto the SECID value you specify for the individual rules (or lines) of a resourceruleset, such as a DASD rule or a LIBMEM rule. You can receive message AX691even though your file contains a SECID rule for the indicated SECID, if there is noreference to the SECID in any resource rule.

UNKNOWN LEVEL OF VSEThe program was unable to determine the level of VSE and therefore could notcontinue. This suggests an internal BIM-ALERT/VSE error. Contact BIMTechnical Support for assistance.

DUPLICATE TABLE ID xxThe OLDTABLE operands and the NEWTABLE operand of the COMBINEstatement must be unique. For example, the following statement would result inmessage AX695 because the table ID 2C is specified twice:

AXPU004 COMBINE OLDTABLE=(2A,2C,2C) NEWTABLE=2D

WARNING - DUPLICATE USER PROFILExxxxxxxxxxxxxxxxxxxxxxxxxxxxWhen the program combines multiple tables to form a new table, and two or more ofthe input tables contain identical user profiles, only the first one encountered can beadded to the new table. Attempting to add the same user profile again results in aVSAM error. The program issues message AX696 and continues with the rest of theCOMBINE operation.

xxx...xxx is replaced with the first 30 bytes of the user profile record's key, whichidentifies the specific user name associated with the user profile record.

AX692

AX695

AX696

Additional Online Error Messages



For an explanation of how online error message numbers are related to the name ofthe program producing the message and descriptions of other online error messages,refer to page 2-61.

ENTER CHANGES AND PRESS ENTER TO SUBMIT JOB -OR-PRESSPF9 FOR SCFL OPTIONS MENURefer to the information in the BIM-ALERT/VSE Security Administrator's Guideabout using the SCFL Screen for an explanation of this message.

PRESS ENTER FOR SCFL OPTIONS MENURefer to the information in the BIM-ALERT/VSE Security Administrator's Guideabout using the SCFL Screen for an explanation of this message.

ENTER CHANGES AND PRESS ENTER TO UPDATE -OR-PRESS PF9FOR SCFL OPTIONS MENU.Refer to the information in the BIM-ALERT/VSE Security Administrator's Guideabout using the SCFL Screen for an explanation of this message.

PRESS ENTER TO SUBMIT DEACTIVATE JOB -OR-PRESS PF9 FORSCFL OPTIONS MENU.Refer to the information in the BIM-ALERT/VSE Security Administrator's Guideabout using the SCFL Screen for an explanation of this message.

SELECT RUN TYPE, ENTER CHANGES, PRESS ENTER TO SUBMITJOB. -OR-PRESS PF9 FOR SCFL OPTIONS MENU.Refer to the information in the BIM-ALERT/VSE Security Administrator's Guideabout using the SCFL Screen for an explanation of this message.

ERRORS DETECTED - CORRECT AND REENTERThe information supplied has not passed all edit tests. Correct the highlighted fieldsand press ENTER.

Introduction

AX700A

AX700B

AX700C

AX700D

AX700E

AX701



JOB SUCCESSFULLY PLACED IN READER QUEUEThe information supplied has been successfully placed into the VSE/POWER readerqueue.

CDLOAD FAILURE - PHASE AXPU003 NOT FOUNDThe phase that builds the jobstream could not be located in the VSE library. Ensurethat the proper library is present in the library search chain.

CDLOAD FAILURE - RC=ccc IN DECIMALThe CDLOAD to load AXPU003 has failed. Refer to the list of CDLOAD returncodes on page 2-84 to determine the source of the problem.

PUTSPOOL ERROR - RC=ccc IN DECIMALThe PUTSPOOL has returned an error. Refer to the IBM publication VSE/POWERInstallation and Operations Guide to determine the meaning of the return code.

ATTACH ERROR - RC=ccc IN DECIMALThe ATTACH has returned an error. The probable cause is that ICCF has a pseudo-partition active. Try again later. If this does not resolve the problem, contact BIMTechnical Support for assistance.

ERROR X'cc' READING/RELEASING SCFL xx RECORD. PGM=AXP700.An error occurred while attempting to read one of the records that store SCFLinformation. xx shows the ID of the record that the program was trying to read. Theprobable cause is that the file is closed. Refer to page 5-3 to determine the meaningof the file access return code X'cc'.

AX702

AX703

AX704

AX705

AX706

AX707



DFHOC ERROR, TCAOCTR = X'cc', PGM=ppppppThe program pppppp tried to open or close AXPCTL with the DFHOC macro andCICS returned hexadecimal error code X'cc'. The possible values for cc are asfollows:

Code Meaning

X'40' An error occurred during an attempt to close the file.

X'80' An error occurred during an attempt to open the file. CICS usually displays amessage on the operator console describing the cause of the error.

X'20' CICS does not have enough main storage to process the DFHOC request.

X'10' Invalid control block name. This is probably a BIM-ALERT/VSE programmingerror. Contact BIM Technical Support for assistance.

This message is usually the result of not setting up FCT properly for AXPCTL.Check your FCT assemble and verify that the FCT entry for AXPCTL is present andthat it is identical to the one shipped in AXPFCT.A. Although changing the settingof any parameter from the values in AXPFCT.A can cause an error, in particular,verify that the following parameters are set:

FILSTAT=CLOSEDLSRPOOL=NONE

ERROR X'cc' UPDATING SCFL xx RECORD. PGM=AX700.An error occurred while attempting to update one of the records that store SCFLinformation. xx shows the ID of the record that the program was trying to read.Refer to page 5-3 to determine the meaning of the file access return code X'cc'.

ERROR X'cc' READING AXPCTL, PGM=ppppppAn error occurred when program pppppp attempted to read the AXPCTL file. Referto page 5-3 to determine the meaning of the file access return code X'cc'.

NO JOB TO SUBMIT - SUBMIT BYPASSEDThe record has been updated with the supplied information, but NO was entered foreach job to submit, and therefore the submit was bypassed.

UNKNOWN LEVEL OF VSEThe program was unable to determine the level of VSE and therefore could notcontinue. This suggests an internal BIM-ALERT/VSE error. Contact BIMTechnical Support for assistance.

AX708

X709

AX710

AX711

AX712



BIM-ALERT/VSE IS NOT ACTIVEA request was made either to display the current BIM-ALERT/VSE system optionsor to deactivate BIM-ALERT/VSE, but BIM-ALERT/VSE is not active. Press PF9to return to the SCFL OPTIONS menu, press PF3 to return to the ALXP Main Menu,or press CLEAR to exit ALXP.

UPDATES COMPLETE. PRESS ENTER FOR SCFL OPTIONS MENU.Your requested JECL/JCL updates have been completed. To proceed with anotherSCFL operation, press ENTER for the SCFL OPTIONS menu and then selectanother SCFL operation. To return to the ALXP Main Menu, press PF3. To exitALXP, press CLEAR.

BIM-ALERT/VSE IS ALREADY ACTIVEThe ACTIVATE BIM-ALERT/VSE option was selected from the SCFL submenu,but BIM-ALERT/VSE is already active on the processor where SCFL is running. Toproceed with the request, fill in the SCFL Screen and press ENTER. (You might dothis to activate BIM-ALERT/VSE on a second processor to which you are connectedvia PNET or some other remote job submittal facility.) To cancel the request andreturn to the SCFL OPTIONS menu, press PF9.

NOT AUTHORIZED TO DISPLAY PASSWORDS. PGM=AXP700.The operator pressed PF11 to display password information on one of the SCFLCONTROL FILE or CURRENT SETTINGS screens, but the password previouslyentered on the SCFL System Options Menu is not correct.

Press PF9 to return to the SCFL System Options Menu, enter the correct password,and select the desired subfunction again.

INVALID JECL/JCL. PGM=AXP700.You selected an SCFL function that requires certain JCL/JECL parameters, but theserequired parameters are invalid or missing. Return to the SCFL submenu, select theSCFL JECL/JCL function, and supply the missing parameters.

Usually this error occurs when you first use SCFL's NETWORK SUBMITTALfunction and have not yet filled in the TARGET SUBLIB and SOURCE SUBLIBfields on the JECL/JCL Screen.

ERRORS DETECTED - CORRECT AND REENTERAXPT has detected invalid or omitted data. If the data is invalid, the incorrect fieldis highlighted on the screen. If the data is missing, the omitted field is filled with

AX713

AX714

AX715

AX716

AX717

AX720



asterisks and is highlighted on the screen. Correct the invalid data or supply themissing data and press ENTER.

NO USERVER INPUTAll of the user verification input fields are missing. You must fill in at least one ofthese fields. This message can occur even if you do not specifically request a userverification. For example, if you enter one of the resource classes for CLASS(indicating that you want a resource authorization) and you do not enter anything forsecurity ID, AXPT assumes that you want it to develop a security ID. To do this,AXPT must perform a user verification and you must supply user verificationinformation as well as resource information. Refer to the BIM-ALERT/VSE SecurityAdministrator's Guide for a list of valid user verification fields and for additionalinformation.

INVALID FUNCTIONAn invalid response was entered in response to the ENTER AUTHORIZATIONCRITERIA OR "N" TO END SESSION message. If you want to end the session,overtype the invalid response with an N. If you want to enter authorization criteria,you must erase the invalid response and leave that field blank; enter yourauthorization criteria in the fields below the ENTER AUTHORIZATIONCRITERIA OR "N" TO END SESSION message.

TABLE UNLOADED. PF3=MENU. ENTER=NEXT FUNCTION.AXPT has successfully unloaded the rules table from the CICS partition GETVISarea. Press CLEAR to end the AXPT session and receive a blank screen. PressENTER to continue the AXPT session. Press PF3 to see the main ALXP menu.Type over the function ID at the upper left of the screen and press ENTER to see aspecific ALXP screen or the BIM-ALERT/CICS-VSE Directory.

ERROR X'cc' LOADING TABLEAn error occurred during an attempt to load the rules table. Refer to the list ofAXPR2 return codes on page 2-83 to determine the source of the problem.

ERROR X'cc' LOADING AXPS2An error occurred during an attempt to CDLOAD AXPS2. Refer to the list ofCDLOAD return codes on page 2-84 to determine the source of the problem.

AX720A

AX721

AX722

AX723

AX724



ERROR ACCESSING TEMP STORAGEAn error was encountered during an attempt to access CICS temporary storage. Runa trace to determine the temporary storage return code and refer page 5-5 for itsmeaning.

RULES TABLE NOT YET UNLOADEDYou pressed CLEAR in response to the ENTER AUTHORIZATION CRITERIA OR"N" TO END SESSION message without first replying N. This means that the rulestable is still loaded in the partition GETVIS area. To end an AXPT session, youmust first reply N to direct AXPT to unload the rules table, then press ENTER, andthen press CLEAR. To continue the AXPT session, press ENTER.

UNKNOWN LEVEL OF VSEThe transaction is unable to determine what level of VSE you are running. Thissuggests an internal BIM-ALERT/VSE error. Contact BIM Technical Support forassistance.

BIM-ALERT/VSE NOT ACTIVEBIM-ALERT/VSE is not yet active.

MUST CHANGE RULESET NAME. MAKE CHANGES, PRESS ENTERYou must change some part of the ruleset name if you want to copy or rename aruleset. Change the table number, dataset name or member name, or volume serialnumber, and then press ENTER.

NOTHING SELECTED. ENTER X, PRESS ENTER.You did not select copy, rename, or one of the status modification operations. Put anX beside one of these, and then press ENTER.

MULTIPLE OPERATIONS SELECTED. RE-ENTER SELECTION, PRESSENTER.You selected more than one of the types of operations. Erase all but one of the Xs,and then press ENTER.

COPY/MODIFY/RENAME COMPLETE.This message is for information only. No corrective action is required.

AX725

AX726

AX727

AX728

AX760

AX761

AX762

AX763



MODIFY STATUS TERMINATED BY OPERATOR.Before carrying out any of the status modification operations, the program requestsconfirmation that the operator wants to continue. If the operator responds N (do notcontinue), the program does not carry out the operation. Instead, it returns to thedataset or resource update screen and displays message AX763A.

ERASE RULESET COMPLETED. PF1=NEXT DATASET. PF3=MENU.This message is for information only. No corrective action is required.

NOT PERMITTED TO MODIFY RULESET NAME ALONG WITH STATUSCHANGE.When you select one of the status modification operations, you must not modify anypart of the ruleset name. Before displaying AX764, the program restores the originalruleset name to the screen. To proceed with the status modification operation, pressENTER.

NO RECORDS FOUND TO COPY/RENAME, PGM=ppppppThe program found no records to copy or rename. pppppp is the name of theprogram that issued the message. This condition is probably caused by aprogramming error. Call BIM Technical Support for assistance in resolving thisproblem.

AX763A

AX763E

AX764

AX765

General BIM-ALERT/VSE Messages



aaaaaaaa RETURNED ERR=cc. NAME=bbbbbbbb.This is a general error message used by many components of BIM-ALERT/VSE toreport error codes returned by subroutines and macros. aaaaaaaa is the name of thesubroutine or macro that returned the error. cc is the error code. In some cases, aname may be associated with a macro. For example, an XPOST macro refers to thename of the XECB to be posted. When the operation involves a name, it is shown inthe error message as bbbbbbbb.

In many cases, the program issuing a macro or calling a subroutine will interpret aspecific return code and issue a more descriptive message instead of the AX801. Forexample, program AXPI1 issues a number of system GETVIS requests. When aGETVIS request returns a storage not available condition, AXPI1 issues messageAX013 INSUFFICIENT SYSTEM GETVIS instead of message AX801. As ageneral rule, the AX801 message is used only for obscure or very infrequentconditions, or for conditions that suggest a programming or design error.

XPCC OperationsParticular values for aaaaaaaa include the following:

XPCCCONN XPCC CONNECTXPCCIDEN XPCC IDENTIFYXPCCSEND XPCC SENDR

Errors that occur in these XPCC operations are described with extended error codesthat are returned by the operating system, in the format bb.cc (for XPCCCONN andXPCCIDEN) or bb.cc.dd.ee (for XPCCSEND). The possible values for these aredescribed in DSECTs that can be generated by the indicated macro, MAPXPCCB orPWRSPL. bb is the value of field IJBXRETC (see DSECT from MAPXPCCB). cc isthe value of field IJBXREAS (see DSECT from MAPXPCCB). dd is the value offield PXPRETCD (see DSECT from PWRSPL). ee is the value of field PXPFBKCD(see DSECT from PWRSPL).

(continued)

AX801



Return Codes for AX801Specific error code values for each subroutine and macro that can be referenced in anAX801 message are, in alphanumeric order, as follows:

AXPI2 Return CodesErrors from this subroutine probably indicate a programming or design error in BIM-ALERT/VSE. Contact BIM Technical Support for assistance in resolving theproblem.

Code Meaning

X'01' BIM-ALERT/VSE is not active.

X'02' Input index parameter is outside permissible range.

X'03' GETVIS error.

AXPASDL Return CodeThe AXPASDL macro displays return code X’04 if the SVA is full or a librarianerror occurs. See the console for related librarian messages.

AXPICCF Return CodesProgram AXPI1 issues the AXPICCF macro at BIM-ALERT startup and shutdowntime. Transactions AX7A and AX7B also issue the macro and display a return codevalue with message AX256.

Code Meaning


X'24' BIM-ALERT programming error.

X'28' AXPHI1 is not in the SVA.

X'2C' Either ICCF is not active, or AX7A or AX7B was run in a non-ICCF partition.

X'30' MCSA identifier was not found. ICCF startup was in progress at the time themacro was issued. This return code might also indicate a BIM-ALERTprogramming error.

X'34' DTSIXP pointer is zeroes. This is probably a BIM-ALERT programming error.

X'38' Submittal monitor was previously established.

AXPIPLX ($SYSOPEN) Return Codes

Code Meaning

X'01' Security (SEC=YES) was not active at IPL.

X'02' CDLOAD of DTSECJCL failed.

X'03 Overlay sequence in DTSECJCL was not found.

(continued)



AXPLG Return Codes

Code Meaning

X'14' An invalid parameter was found which probably indicates a programming error.


X'40' BIM-ALERT/VSE logger is not active.

X'44' BIM-ALERT/VSE logger is present but IDLE.

X'48' BIM-ALERT/VSE log file CLOSE is in progress.

AXPL5 Return CodesExcept as indicated, errors from this subroutine probably indicate a programming ordesign error in BIM-ALERT/VSE. Contact BIM Technical Support for assistance inresolving the problem. The exception is code X'01', which simply means that there isnot enough partition GETVIS for the program to continue. In that case, resubmit thejob in a partition with more GETVIS.

Code Meaning

X'01' Not enough GETVIS was found for record work area.

X'02' An invalid DEST parameter was found.

X'03' BIM-ALERT/VSE anchor was not present.

X'04' An invalid TYPE parameter was found

X'05' An invalid or missing ACTION was detected.

X'06' BIM-ALERT could not locate ACEE. This return code is not serious if you arerunning an old version of BIM-ALERT while converting your rules table.

AXPL6 Return CodesExcept as indicated, errors from this subroutine probably indicate a programming ordesign error in BIM-ALERT/VSE. Contact BIM Technical Support for assistance inresolving the problem.

Code Meaning

X'01' AXPLG MF=BUILD returned too large a record.

X'02' AXPLG MF=BUILD R0 is not equal to SMF89LEN.

X'03' BIM-ALERT/VSE is not active. This is not a serious error.

(continued)



AXPL8 Return CodesExcept as indicated, errors from this subroutine probably indicate a programming ordesign error in BIM-ALERT/VSE. Contact BIM Technical Support for assistance inresolving the problem.

Code Meaning

X'01' AXPLG MF=BUILD returned too large a record.

X'02' AXPLG MF=BUILD R0 is not equal to SMF89LEN.

X'03' BIM-ALERT/VSE is not active. This is not a serious error.

X'04' ACTION parameter is not RULES.

AXPR2 Return CodesPrograms that invoke AXPR2 are supposed to check specifically for return codes 01,03, 04, and 05 and then issue more descriptive error messages if any of those codesis found. Therefore, if an AX801 message is issued with any of those codes, itprobably indicates a programming error. Contact BIM Technical Support to resolvethe problem.

Code Meaning

X'01' BIM-ALERT/VSE is not active. This is probably a programming error.

X'02' Rules update is already in progress in another partition. Resubmit the job after thatpartition finishes.

X'03' An invalid security ID or name is not equal to phase name.

X'04' BIM-ALERT could not find enough system GETVIS to load table.

X'05' Phase length is incorrect.

X'06' Backlevel rules table. Reassemble the table using the current version of BIM-ALERT/VSE.

X'07' BIM-ALERT could not find enough partition GETVIS for work area.

X'08' Phase was not found.

(continued)



CDLOAD Return Codes

Code Meaning

X'04' The size of the partition's GETVIS area is 0K.

X'08' The length of the requested GETVIS storage is negative.

X'0C' No more storage is available in the GETVIS area.

X'10' The partition CDLOAD directory is full.

X'14' The phase does not exist in the library.

X'20' A hardware failure occurred in the requested real partition GETVIS area.

GETVIS Return Codes

Code Meaning

X'04' The size of the partition's GETVIS area is 0K.

X'08' The specified length is negative.

X'0C' No more storage is available in the GETVIS area.

X'20' A hardware failure occurred in the requested real partition GETVIS area.

LOCK Return Codes

Code Meaning

X'04' Resource is not available because it is already owned exclusively.

X'08' LOCK table space is full.

X'0C' LOCK request is inconsistent with previous LOCK requests.

X'10' LOCK request will cause deadlock condition.

X'14' An error was found in the DTL format.

X'18' LOCK request is for a resource already owned.

X'1C' LOCK disk file is full.

X'20' LOCK request is for a shared DASD file, but the volume is not mounted.

X'24' An I/O error was found in the disk LOCK file.

(continued)



UNLOCK Return Codes

Errors from this macro probably represent a programming or design error in BIM-ALERT/VSE. Contact BIM Technical Support for assistance in resolving theproblem.

Code Meaning

X'04' The requesting task does not own the resource.

X'08' An error was found in the DTL format.

XDEFINE Return CodesXDEFINE designates errors from XECBTAB TYPE=DEFINE.

Code Meaning

X'04' The named XECB is already defined. This probably indicates a programmingerror.

X'08' The XECB table is full.

XDELETE Return CodesXDELETE designates errors from XECBTAB TYPE=DELETE. Errors from thismacro probably indicate a programming or design error in BIM-ALERT/VSE.Contact BIM Technical Support for assistance in resolving the problem.

Code Meaning

X'04 The named XECB was not found in the XECB table.

X'08' The task requesting the DELETE did not define the XECB.

XPOST Return CodesErrors from this macro probably indicate a programming or design error in BIM-ALERT/VSE. Contact BIM Technical Support for assistance in resolving theproblem.

Code Meaning

X'04' The named XECB is not defined in the XECB table.

X'0D' Some other task defined the named XECB with ACCESS=XPOST.

X'0E' The named XECB has already been posted or the task that issued the XPOSTmacro also defined the XECB with ACCESS=XWAIT.

(continued)



XWAIT Return CodesErrors from this macro probably indicate a programming or design error in BIM-ALERT/VSE. Contact BIM Technical Support for assistance in resolving theproblem.

Code Meaning

X'04' The named XECB is not defined in the XECB table.

X'08' The other task using this XECB has broken communication without issuing anXPOST.

X'0D' Some other task defined the XECB with ACCESS=XWAIT.

X'0E' The task that issued the XWAIT also defined the XECB with ACCESS=XPOST orsome other task is already waiting on the XECB.

PHASE=xxxxxxxx NOT FOUND BY CDLOADThe program attempted to CDLOAD phase xxxxxxxx, but it was not found in anylibrary. Adjust the PHASE SEARCH chain to include the library in which the phaseis located.

INTERNAL ERROR IN aaaaaaaa, CODE=ccA number of programs contain "armor" to guard against the occurrence of certainimprobable conditions. When one of these conditions occurs, the program issuesAX803. aaaaaaaa is the name of the failing module. cc is a code that represents thespecific condition encountered. Contact BIM Technical Support for assistance inresolving the problem.

ERROR X'cc' ON TS. Q=qqqqqqqq. PGM=ppppppCICS returned an error code from a temporary storage request. X'cc' is thehexadecimal return code.

qqqqqqqq is the name of the temporary storage queue. pppppp is the name of theprogram that generated the error. Refer to page 5-5 for the meaning of the temporarystorage return code X'cc'.

ERROR X'cc' FROM S1A000. PGM=pppppp.The BIM-ALERT/VSE audit trail module (S1A000) returned a hexadecimal returncode of X'cc'. If cc has a value of FF, then the error is a temporary storage error. Inthis case, set AUXTRACE on, reproduce the error, and examine the AUXTRACEoutput to determine the specific temporary storage error. If cc has a value other thanFF, it is a CICS file access return code. Refer to page 5-3 to determine the meaningof the file access return code X'cc'. pppppp is the name of the program that invokedS1A000.

AX802

AX803

AX804

AX805



NEEDS TWASIZE=nnnnThe ALXP driver program (AXP10000) examines the PCT to determine theTWASIZE specified for the ALXP transaction. If the specified size is less than therequired size, AXP10000 modifies the TWASIZE value in the PCT entry in CICSstorage, issues message AX806, and then terminates. To continue, press CLEAR,reenter ALXP, and then press ENTER.

Message AX806 will be generated on the first execution of ALXP each time CICS isstarted and each time the ALXP transaction is installed with CEDA. To eliminate itsbeing generated, modify the TWASIZE in the PCT assembly or in the CEDA entry.Refer to the BIM-ALERT Installation and Operations Guide to determine therequired TWASIZE value.

BIM-ALERT/VSE SECURITY FILE IS NOT CORRECT VERSION.PGM=pppppp.The version of the ALERTXP security file is inconsistent with the version of BIM-ALERT/VSE that you are executing. This probably means that you forgot to executeprogram AXPU006 to convert the file. For more information about converting thesecurity file, refer to the BIM-ALERT Installation and Operations Guide. pppppp isthe name of the program that was executing. After issuing message AX807, theprogram terminates.

ERROR X'cc' READING SECURITY FILE. PGM=pppppp.When the program pppppp tried to read the ALERTXP security file to verify that itwas the correct version, CICS returned a file access error. cc is the CICS file accessreturn code. Refer to page 5-3 to determine the meaning of the file access returncode X'cc'.

SECURITY FILE CONTROL RECORD NOT FOUND. PGM=ppppppWhen the program pppppp tried to read the security file control record to verify thatthe file was the correct version, VSAM returned a "not found" indication. Thisprobably means that the file has been corrupted.

LOG FILE TAPE IS BACKLEVELThe input log file tape was created with a version of BIM-ALERT/VSE prior to 4.90.Either use a pre-4.90 version of the report program to generate the report, or convertthe tape file to the 4.90 format with program AXPL14. For more information aboutprogram AXPL14, refer to the BIM-ALERT Installation and Operations Guide.

AX806

AX807

AX807A

AX807B

AX808



UNABLE TO RESOLVE $$ JOB STATEMENT. PGM=xxxxxxxxSome of the submittal monitors parse the $$ JOB statement from the input file inorder to insert user ID information into the jobstream. This process requires that thesubmittal monitor be able to modify the input $$ JOB statement. If the syntax of theinput $$ JOB statement is such that BIM-ALERT is unable to make the necessarymodification to the $$ JOB statement, message AX809 is issued.

Possible causes for this condition are:

• The input $$ JOB statement contains a POWER syntax error.

• The input JOB statement is not blank in column 5 (* $$JOB instead of * $$JOB), it is not blank in column 71, and it is not continued.

• The BIM-ALERT submittal monitor program contains an error.

After issuing message AX809, the submittal monitor either aborts the submittal orallows the file to be submitted without the BIM-ALERT user ID information.

SUBMITTAL HAS BEEN ABORTED. PGM=xxxxxxxxThe BIM-ALERT submittal monitor program has aborted a submittal. See theexplanation of message AX809 for possible causes of this.

JOB SUBMITTED WITHOUT USERID INFORMATION. PGM=xxxxxxxxThe BIM-ALERT submittal monitor program has submitted a jobstream with noBIM-ALERT user ID information. See the explanation of message AX809 forpossible causes of this.

AX809

AX809A

AX809B

3-1

3

BIM-ALERT/CICS Messages

This chapter describes the BIM-ALERT/CICS messages and the actions to take inresponse to them.

About This Chapter....................................................................................................3-2Initialization Messages ..............................................................................................3-3Online Driver Messages...........................................................................................3-13System Parameter Maintenance Messages...............................................................3-15Internal Processing Messages ..................................................................................3-16Online File Maintenance Messages .........................................................................3-24Activation and Deactivation Messages ....................................................................3-32Sign-on and Sign-off Messages ...............................................................................3-35Batch/Utility Program Messages .............................................................................3-40Informational Messages ...........................................................................................3-58Violation Messages..................................................................................................3-71

About This Chapter


About This Chapter

This chapter describes BIM-ALERT/CICS messages. These messages begin with theletters GK and are divided into the following categories:

Message Numbers Description

GK000 to GK099 Issued by the BIM-ALERT/CICS initialization routines

GK100 to GK109 Issued by program S10000, the online driver program

GK110 to GK119 Issued by program S1S999, the system parameter maintenanceprogram

GK120 to GK199 Issued by internal processing routines

GK200 to GK249 Issued by the online file maintenance programs

GK250 to GK299 Issued by programs that activate or deactivate resources

GK300 to GK400 Issued by modules that handle terminal and operator sign-onand sign-off processing

GK500 to GK699 Issued by the batch and utility programs

GK700-GK999 Informational or instructional messages

This chapter also describes BIM-ALERT/CICS messages written to the log file andto the operator (when applicable) after a violation has occurred.

Initialization Messages

Chapter 3. BIM-ALERT/CICS Messages 3-3


The messages produced during BIM-ALERT/CICS initialization are in the numberrange of GK000 to GK099. This range is further subdivided as follows:

MessageNumbers Description

GK000 to GK024 Produced during UCOP/DCOP processing. These messages are sentto the terminal from which the request was issued.

GK025 to GK039 Informational messages. These messages are routed to the systemoperator console.

GK040 to GK059 Indicate an abnormal condition. In general, these messages areproduced because some part of the installation process was notcompleted successfully. They are routed to the system operatorconsole.

GK060 to GK064 Require a response from the operator's console.

GK065 to GK074 Indicate an abnormal condition: either an internal error occurred orsome part of the installation process was not completed successfully.These messages all concern failures to acquire storage, install hooks,or load control modules.

GK075 to GK084 Indicate errors encountered during an attempt to access the BIM-ALERT/CICS control files during initialization.

GK085 to GK099 Indicate an abnormal condition related to building the BIM-ALERT/CICS security tables.

PERMANENT SECURITY OPTIONS UPDATE COMPLETE (GK000)The update of the permanent security options was completed successfully. The nexttime BIM-ALERT/CICS is initialized using the PLT startup, the new options will bein effect.

NO OPTIONS REQUESTED - SECURITY STILL INACTIVE (GK001)UCOP was executed to initialize security, but no options were selected from thescreen and therefore security was not initialized.

SECURITY SYSTEM NOT ACTIVE - OPTIONS NOT AVAILABLE (GK002)The DCOP function was requested to display the current security options, butsecurity is not active.

Introduction

GK000

GK001

GK002



INCORRECT SPECIFICATIONS - CORRECT AND RE-ENTER (GK003)UCOP or UPOP is being executed to change the current or permanent options, butthe options selected on the screen are not logically possible (that is, either both orneither of the ON and OFF options have been selected).

SYSTEM SECURITY FILE(S) NOT FOUND IN FCT - XXXXXXXX (GK004)At least one of the files necessary for BIM-ALERT/CICS to function (S1SCTY,S1SECLG, or S1SAUDT) was not found in the FCT. Check both the FCT assemblyto be sure it cataloged properly and the CICS startup deck to ensure that you areusing the proper FCT suffix (the FCT=xx parameter in the SIT overrides).

S001 IS NOT EXECUTABLE FROM A TERMINAL (GK006)S001 was entered on a terminal. This is an internal BIM-ALERT/CICS transaction;it should never be run from a terminal session. If it were allowed to run on aterminal and BIM-ALERT/CICS were active, it could cause CICS to abend.

ERROR DETECTED ON SYSTEM SECURITY FILE -EIBRCODE=X'XXXXXXXX' - XXXXXXXX (GK010)An error has been returned from the file access request. The EIBRCODE valueindicates the problem. Refer to page 5-3 to determine the meaning of the file accessreturn code.

INITIALIZING BIM-ALERT/CICS VERS XXXXXXXX PTF LEVELXXXXXXXX (GK025)This message displays the release level of the BIM-ALERT/CICS system beinginitialized.

INITIALIZING BIM-ALERT/CICS FOR CICS XXXXXXXX (GK025A)This message displays the level of CICS that is running on your system.

BIM-ALERT/CICS EXPIRES IN 30 DAYS OR LESS (GK026)This message informs you that your BIM-ALERT/CICS product code will expire in30 days or less. The message appears with each initialization beginning 30 daysprior to expiration. Beginning 7 days prior to expiration, the message requires anoperator response before initialization can continue. Contact your BIM accountmanager for a new product code.

GK003

GK004

GK006

GK010

GK025

GK025

GK026



XXXXXXXX VVVVVVVVVVVS CAN BE SECURED (GK027)This message specifies the maximum number (XXXXXXXX) of transactions,programs, files, maps, or field-level resources (VVVVVVVVVVV) that can be securedduring this session of CICS. This number is calculated by extracting the currentcount for each resource type and adding the number of extra entries (specified on theUPAR panel) to it.

ISSUING STORAGE REQUEST FOR XXXXXXXX BYTES - XXXXXXXX(GK029)XXXXXXXX bytes are required to build one of the BIM-ALERT/CICS securitytables. The end of the message specifies which BIM-ALERT/CICS program issuedthe request, which in turn signifies which table is being built. The following tableexplains which program builds which table.

This Program Builds This Table

S1S002 Terminal table

S1S003 Operator table

S1S004 Transaction table

S1S005 Program table

S1S006 File table

S1S007 Map tables

S1S011 Field-level resource table

The other tables are built only if security for that resource type is being turned on.

USING SHARED TABLE DATED XXXXXXXX - XXXXXXXX (GK030)The security table has already been built in shared storage, either by a previousstartup of this CICS system, or by another region or partition in an MRO complex.The date the table was built is reported in Julian format. The end of the messagespecifies which BIM-ALERT/CICS program issued the request, which in turnsignifies which type of table has been located. See the explanation for messageGK029.

BIM-ALERT/CICS INITIALIZATION BEGINS USING CONTROL SUFFIXXXXXXXXX (GK031)This message is the first message issued during PLT startup. It identifies the controlsuffix to be used for this session.

GK027

GK029

GK030

GK031



MRO OPTION SELECTED - SHARED TABLES LOCATED (GK032)A nonzero control suffix has been specified, and the tables for that suffix have beenbuilt previously.

OPERATOR AND TERMINAL TABLES WILL BE RESET (GK033)Since the shared tables have been built previously, BIM-ALERT/CICS must ensurethat they are marked as signed off before giving control to CICS. This ensures thatusers do not mistakenly receive other users' authority and also prevents unwarrantedterminal and operator timeouts.

BIM-ALERT/CICS TABLES WILL BE REFRESHED (GK034)A nonzero control suffix has been specified, but the tables for this control suffix donot yet exist. They will be built during this initialization.

BIM-ALERT/CICS INITIALIZATION REQUEST ISSUED (GK035)The request for BIM-ALERT/CICS initialization has been processed, and the actualinitialization procedure will begin shortly.

BIM-ALERT/CICS INITIALIZATION COMPLETE (GK039)The initialization procedure has completed successfully. Security is now activatedaccording to the options specified either in the permanent options (PLT startup) or inthe current options (UCOP startup).

SYSTEM PARAMETERS MISSING - XXXXXXXX (GK040)At least one of the required UPAR or UTOP parameters is not specified. Determinewhich parameters are missing, add them, and try the initialization again.

PERMANENT OPTIONS ALL OFF (GK041)A PLT startup has been requested. However, the permanent options record has notbeen updated via the UPOP transaction, and therefore BIM-ALERT/CICS has noinstructions about which options to initialize. Initializing BIM-ALERT/CICS in thismode locks everyone out of the system.

AUTOMATIC STARTUP DENIED (GK042)This message is issued in conjunction with GK041. In order for automatic PLTstartup to take place, the UPOP transaction must be executed and some options must

GK032

GK033

GK034

GK035

GK039

GK040

GK041

GK042



be selected in the ON column. When automatic PLT is denied, security can beinitialized only via UCOP.

MINIMUM CWA SIZE FOR SECURITY NOT SPECIFIED (GK043)No minimum size was specified in the WRKAREA= parameter in the SIT overrides.The default value of 512 will be used.

BIM-ALERT/CICS uses the last 64 bytes of the CWA as an anchor table for securityprocessing. Accordingly, the minimum number that can be specified in theWRKAREA= parameter is 64. You should specify a value of 64 or greater.

PRODUCT PASSWORD IS INVALID (GK044)The product password is not valid for BIM-ALERT/CICS. Contact your BIMaccount manager to obtain a valid product password.

CONTACT SECURITY ADMINISTRATOR *-*-* (GK045)This message is produced in conjunction with several other initialization messages toremind the operator whom to contact to correct the situation.

PRODUCT PASSWORD HAS EXPIRED (GK046)The BIM-ALERT/CICS product password has expired. Security cannot beinitialized until a valid product password is applied. Contact your BIM accountmanager to obtain a valid product password.

SECURITY CANNOT BE ACTIVATED *-*-* (GK047)This message is produced in conjunction with GK046.

SECURITY PROGRAM XXXXXXXX - NOT FOUND IN PPT (GK048)The BIM-ALERT/CICS program XXXXXXXX is not in the PPT. Security cannot beactivated without this program. Verify that the PPT assembled and catalogedproperly, and that the suffix specified in the SIT parameters (PPT = xx) is for thecorrect PPT.

SECURITY SYSTEM DATE ERROR DETECTED (GK049)The date conversion routines within the initialization modules failed to produce avalid date. This indicates an internal error or storage corruption. Contact BIMTechnical Support for assistance.

GK043

GK044

GK045

GK046

GK047

GK048

GK049



REPLY GO OR CANCEL (GK060)Some abnormal condition has been detected that may prevent BIM-ALERT/CICSfrom initializing properly. Reply GO to continue with CICS initialization. ReplyCANCEL to cancel CICS.

INVALID RESPONSE (GK061)The only valid responses to message GK060 are GO and CANCEL. If you enter anyother response, GK060 is reissued to allow you to enter a valid response.

PRESS ENTER - CALL BIM TECHNICAL SUPPORT. (GK062)This message is issued in conjunction with several of the preceding error messagesindicating problems with your product code. To obtain a valid product code, contactyour BIM account manager.

LOAD FAILURE - RETURN CODE = XXXXXXXX - MODULE = XXXXXXXX- XXXXXXXX (GK065)An error occurred during an attempt by the specified program to load the specifiedmodule. The return code indicates why the load failed. Refer to page 5-6 for themeaning of the load request return code.

SEVERE ERROR IN XXXXXXXX - CICS CANCELLED (GK066)This message is issued in conjunction with other BIM-ALERT/CICS messages thatexplain which severe error occurred. The initialization program issuing the messageis identified.

CICS LOAD FAILURE - MODULE = XXXXXXXX (GK067)An error occurred while issuing a CICS load for the BIM-ALERT/CICS moduleXXXXXXXX. The error probably results from a problem with the PPT. Verify thatthe PPT specified in the SIT overrides is the one containing the BIM-ALERT/CICSmodules, or, if you are using RDO, that all modules have been defined correctly.

STORAGE FAILURE - RETURN CODE = XXXXXXXX (GK068)BIM-ALERT/CICS's storage request to the operating system was denied for thereason specified. Most likely, there is not enough operating system storage(GETVIS) available. Refer to page 5-6 for the meaning of the storage request returncode XXXXXXXX.

GK060

GK061

GK062

GK065

GK066

GK067

GK068



VVVVVVVVVVV MONITOR INITIALIZATION ERROR (GK069)An error occurred during an attempt to install the specified BIM-ALERT/CICSmonitor. The most likely cause of this is that another software product has alteredthe pointers to the CICS control modules in the CSA. Placing BIM-ALERT/CICSfirst in the PLT will probably correct this error if you use a PLT startup. If this doesnot work, contact BIM Technical Support.

MAP MONITOR INITIALIZATION ERROR XXXXXXXX (GK069A)An error occurred during an attempt to install the specified BIM-ALERT/CICS mapmonitor. The most likely cause of this is either that an incorrect version of BIM-ALERT/CICS is running or that another software package has altered the pointers tothe CICS map control modules. Placing BIM-ALERT/CICS first in the PLT willprobably correct this error if you use a PLT startup. If this does not work, contactBIM Technical Support.

FIELD LEVEL RESOURCE INITIALIZATION ERROR (GK069B)An error occurred during an attempt to install the BIM-ALERT/CICS field-levelsecurity monitor (S1S180 or S1S181). The most likely cause of this is that anothersoftware product has altered the pointers to the CICS control modules in the CSA.Placing BIM-ALERT/CICS first in the PLT will probably correct this error if youuse a PLT startup. If this does not work, contact BIM Technical Support.

DLI MONITOR INITIALIZATION ERROR - XXXXXXXX (GK069C)An error occurred during an attempt to install the BIM-ALERT/CICS DLI monitor.The most likely cause of this is either that an incorrect version of BIM-ALERT/CICSis running or that another software package has altered the pointers to DL/I in thepartition COMREG. Placing BIM-ALERT/CICS first in the PLT will probablycorrect this error if you use a PLT startup. If this does not work, contact BIMTechnical Support.

XXXXXXXX IN SHARED STORAGE - VVVVVVVVVVV SECURITY NOTACTIVATED (GK070)The specified CICS control module (DFHxxx) is loaded in shared storage (SVA) andtherefore BIM-ALERT/CICS cannot make the modifications necessary to install thesecurity monitor VVVVVVVVVVV. Refer to the BIM-ALERT Installation andOperations Guide to determine which CICS control modules may not reside inshared storage.

GK069

GK069

GK069

GK069

GK070



ERROR ACCESSING SECURITY FILE S1SCTY - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK075)An error occurred during an attempt to access the security file. Refer to page 5-3 forthe meaning of the file access return code X'XXXXXXXX'.

VVVVVVVVVVV CONTROL RECORD NOT FOUND - XXXXXXXX (GK076)A NOTFND condition was returned to BIM-ALERT/CICS in response to a readrequest for the control record for resource type VVVVVVVVVVV. This indicateseither an internal error or file corruption. Please contact BIM Technical Support,and have an IDCAMS listing of the S1SCTY file available.

LOCAL SYSID FOR XXXXXXXX FILE NOT ACTIVE - XXXXXXXX (GK077)The CICS system that has the identified BIM-ALERT/CICS file defined as local isnot active. You may direct BIM-ALERT/CICS to retry in one minute or to shutdown by responding appropriately to message GK078, which is issued inconjunction with GK077.

REPLY WAIT OR CANCEL (GK078)This message is issued with message GK077. If you reply WAIT, BIM-ALERT/CICS waits one minute and then retries the file access. If the file accessfails again, BIM-ALERT/CICS issues messages GK077 and GK078 again. If youreply CANCEL, BIM-ALERT/CICS abends CICS.

DELETE FAILURE - RETURN CODE = XXXXXXXX - MODULE =XXXXXXXX - XXXXXXXX (GK079)An error occurred during an attempt to delete the specified module. Refer to page 5-6 for the meaning of the load request return code.

ERROR ACCESSING SECURITY LOG FILE S1SECLG - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK080)An error occurred during an attempt to write initialization messages to the BIM-ALERT/CICS log file. Refer to page 5-3 for the meaning of the file access returncode.

VVVVVVVVVVV TABLE VALIDITY ERROR - XXXXXXXX (GK085)The BIM-ALERT/CICS security table for resource type VVVVVVVVVVV has beenlocated in shared storage, but it has been corrupted. Run S1U010 to clear the sharedtables and restart CICS.

GK075

GK076

GK077

GK078

GK079

GK080

GK085



BIM-ALERT/CICS TABLES BEING BUILT IN ANOTHER REGION (GK086)One of the initialization programs has detected that the table it is responsible forbuilding is already being built in some other CICS region. Please wait 10-15seconds, then press ENTER to try again.

VVVVVVVVVVV TABLE BEING BUILT IN ANOTHER REGION - PRESSENTER TO RETRY - XXXXXXXX (GK086A)The initialization program XXXXXXXX has detected that the table it is responsiblefor building is already being built in some other CICS region. Please wait 10-15seconds, then press ENTER to try again.

EXIT VALUE VALIDITY ERROR (GK087)The terminal security table for the current control suffix has been located in sharedstorage, but the user-exit value in the current system options does not match thevalue used to build the existing table. Either change the exit value in the currentsecurity options (on UPAR), or execute S1U010 to free the existing table and allowthe initialization module to rebuild it using the current exit value.

TERMINAL SECURITY INITIALIZATION ERROR (GK090)An error occurred during an attempt to locate a defined terminal. Contact BIMTechnical Support.

TERMINAL XXXXXXXX NOT IN TERMINAL CONTROL TABLE (GK091)Terminal XXXXXXXX is defined in the BIM-ALERT/CICS security file as status A,but it does not exist in the TCTTE. Change the terminal status to P, or add theterminal to the TCTTE, or reply GO to message GK060 to continue initialization.

SECURITY FOR TERMINAL XXXXXXXX NOT ACTIVATED (GK092)This message is issued if you reply GO to message GK091 and thereby permit BIM-ALERT/CICS initialization to continue even though terminal XXXXXXXX cannot belocated in the TCTTE.

TERMINAL XXXXXXXX NOT A 3270 DEVICE TYPE (GK093)Terminal XXXXXXXX is defined in the security file as a secured terminal, but it isnot defined in the TCTTE as a 3270 device type. This normally occurs if you changea terminal ID to a printer or another device type. You may direct BIM-ALERT/CICSto continue by responding GO to the GK060 message issued on the operator console.

GK086

GK086

GK087

GK090

GK091

GK092

GK093



XXXXXXXX TRANSACTION NOT CORRECT FOR BIM-ALERT/CICS(GK094)The transaction XXXXXXXX (CSSN or CSSF) does not have the correct BIM-ALERT/CICS program name specified in the PCT. This message is informationalonly.

XXXXXXXX PROGRAM REPLACED BY S1S610 (GK095)BIM-ALERT/CICS has corrected the condition that prompted message GK094 bysubstituting program S1S610 for the specified program.

OVERFLOW CAUSED BY FILE ENTRY XXXXXXXX (GK097)The storage requested for the transaction security table is not sufficient to hold all ofthe secured transactions defined in the file. This is probably due to an internal erroror a corrupted transaction control record. Please have an IDCAMS print of thesecurity file available and contact BIM Technical Support.

GK094

GK095

GK097

Online Driver Messages



The messages in the range of GK100 to GK109 are issued by program S10000.S10000 is the driver program of the SCTY transaction, which is used for all onlinefile maintenance, activation and deactivation, and administrative functions.

NO PROCESSING FUNCTION REQUESTED ... RE-ENTER (GK100)Either you pressed an incorrect PF key or you did not enter X next to the desiredfunction on the menu.

SECURITY FUNCTIONS ARE NOT AUTHORIZED FROM UNSECUREDTERMINALS (GK101)When BIM-ALERT/CICS is active, you must be signed on to a BIM-ALERT/CICSsecured terminal to perform security functions.

SECURITY ADMINISTRATOR MUST BE SIGNED ON TO PROCESSTRANSACTION XXXXXXXX (GK102)When BIM-ALERT/CICS is active, you must be signed on to a BIM-ALERT/CICSsecured terminal as a BIM-ALERT/CICS administrator to perform securityfunctions.

A SUB-ADMINISTRATOR IS NOT AUTHORIZED TO PROCESSTRANSACTION XXXXXXXX (GK103)When BIM-ALERT/CICS is active, many of the functions on the menu screens (forexample, ASTR and ASPR) can be performed only by main administrators.

SUB-ADMINISTRATOR NOT AUTHORIZED TO PROCESS TERMINALSECURITY (GK104)A subadministrator with operator class O is authorized to perform only operatorsecurity functions.

XXXXXXXX IS NOT A VALID SECURITY TRANSACTION (GK105)The function XXXXXXXX is not one of the options available from the menu.

Introduction

GK100

GK101

GK102

GK103

GK104

GK105



ERROR ACCESSING TEMPORARY STORAGE - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK106)An error occurred during an attempt to access temporary storage. The EIBRCODEvalue indicates the reason for the failure. Refer to page 5-5 for the meaning of thetemporary storage return code.

GK106

System Parameter Maintenance Messages


System Parameter Maintenance Messages

The messages in the range of GK110 to GK119 are issued by the system parametermaintenance program S1S999. These messages are received when executing theupdate system or terminal and operator transactions (UPAR, UTOP), or thecorresponding display transactions (DPAR, DTOP).

PARAMETER SPECIFICATIONS UPDATE COMPLETE (GK110)The requested updates have been successfully processed.

ERRORS DETECTED ... CORRECT/RE-ENTER (GK111)Errors were detected while editing the proposed updates. The fields in error aredisplayed in high intensity, and the explanation to the right of the field explains theerror detected.

LOAD FAILURE - RETURN CODE = XXXXXXXX - MODULE = XXXXXXXX- XXXXXXXX (GK112)An error occurred during an attempt to load module XXXXXXXX. The load requestreturn code XXXXXXXX indicates why the load failed. Refer to page 5-6 for themeaning of the load request return code.

ERROR ACCESSING SECURITY FILE S1SCTY - EIBRCODE =X'XXXXXXXX' (GK115)An error occurred during an attempt to access the security file. Refer to page 5-3 forthe meaning of the file access return code X'XXXXXXXX'.

ERROR ACCESSING SECURITY AUDIT FILE S1SAUDT - EIBRCODE =X'XXXXXXXX' (GK116)An error occurred during an attempt to update the audit file. Refer to page 5-3 forthe meaning of the file access return code X'XXXXXXXX'.

Introduction

GK110

GK111

GK112

GK115

GK116

Internal Processing Messages



The messages in the range of GK120 to GK199 are issued by the internal processingroutines of BIM-ALERT/CICS, including the inactive time-limit processing,violation logging, and violation reporting routines. Where applicable, the name ofthe program issuing the message is reported at the end of the message; it is denotedby XXXXXXXX.

ERROR ACCESSING SECURITY FILE S1SCTY - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK120)An error occurred during an attempt to access the security file. The program issuingthe message is identified by XXXXXXXX. Refer to page 5-3 for the meaning of thefile access return code X'XXXXXXXX'.

ERROR ACCESSING SECURITY LOG FILE S1SECLG - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK121)An error occurred during an attempt to update the log file. The program issuing themessage is identified by XXXXXXXX. Refer to page 5-3 for the meaning of the fileaccess return code X'XXXXXXXX'.

TIME ERROR DETECTED IN TERMINAL SCHEDULER (GK130)The terminal scheduler monitor S1S140 has failed to convert a valid clock time.This is due either to an internal error in the monitor or to storage corruption. ContactBIM Technical Support for assistance.

DATE ERROR DETECTED IN TERMINAL SCHEDULER (GK131)The terminal scheduler monitor S1S140 has failed to convert a valid date. Thisindicates either an internal error in the monitor or storage corruption. Contact BIMTechnical Support for assistance.

BIM-ALERT/CICS NOW USING PROFILES FOR XXXXXXXX (GK132)The terminal scheduler monitor S1S140 has verified that the terminal security tablehas been initialized with the correct day's (XXXXXXXX) access times.

Introduction

GK120

GK121

GK130

GK131

GK132



CALCULATED DAY NOT 1-7 IN S1S140 (GK133)The terminal scheduler monitor S1S140 has failed to calculate the day of the week.This indicates either an internal error in the monitor or storage corruption. ContactBIM Technical Support for assistance.

CICS TERMINAL-ID XXXXXXXX, CUU UNIT XXXXXXXX RESET FROMVSE (GK140)The terminal ID XXXXXXXX has been reset to VM, either because of a user requestor because of inactive time-limit processing parameters.

EXTRACT ERROR - CICS TERMINAL-ID XXXXXXXX NOT RESET FROMVSE (GK141)The terminal disconnect program S1S147 failed to determine the physical deviceaddress (CUU) of the terminal to be reset to VM. This probably indicates an internalerror in S1S147. Contact BIM Technical Support for assistance.

LTA UNAVAILABLE - CICS TERMINAL-ID XXXXXXXX NOT RESET FROMVSE (GK142)Ten successive attempts have been made to load the transient in order to perform theVM disconnect, but the VSE logical transient area (LTA) has remained unavailable.Rather than keeping CICS waiting for the LTA, BIM-ALERT ignores the requestand processing continues without the disconnect being issued.

ERROR ACCESSING TEMPORARY STORAGE - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK143)An error has been returned in response to a temporary storage request. Refer to page5-5 to determine the meaning of the temporary storage return code X'XXXXXXXX'.

ERROR CANCELLING STARTED TASK - EIBRCODE = X'XXXXXXXX' -XXXXXXXX (GK144)An error has been returned in response to an interval control request to cancel theS145 task. Processing continues after the message. Refer to page 5-4 to determinethe meaning of the interval control return code X'XXXXXXXX'.

GK133

GK140

GK141

GK142

GK143

GK144



ERROR WRITING TO TEMPORARY STORAGE - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK145)An error has been returned in response to a temporary storage PUTQ request. Referto page 5-5 to determine the meaning of the temporary storage return codeX'XXXXXXXX'.

TERMINAL XXXXXXXX SECURITY RECORD NOT FOUND - XXXXXXXX(GK146)The profile for terminal XXXXXXXX could not be located in the security file.Processing continues with the next terminal.

ERROR INITIATING INACTIVE TIME LIMIT PROCESSING - EIBRCODE =X'XXXXXXXX' XXXXXXXX (GK147)An error has been returned in response to an attempt by an interval control task toinitiate inactive time-limit processing. Processing continues without timing out theoperator or terminal. Refer to page 5-4 to determine the meaning of the intervalcontrol return code X'XXXXXXXX'.

TERMINAL XXXXXXXX BINARY SEARCH FAILURE - XXXXXXXX (GK148)The violation processor could not locate terminal XXXXXXXX in the BIM-ALERT/CICS terminal security table. The message is produced on the console andthe task is abended. This probably indicated either data corruption or an internalerror in BIM-ALERT/CICS. Contact BIM Technical Support for assistance.

SECURITY VIOLATION REPORTING ERROR DETECTED (GK150)An error has occurred during an attempt to perform real-time violation routing to thespecified device.

INVALID FROM DATE ... RE-ENTER (GK160)The FROM date entered on the DVIO, PVIO, or DAUD screen is invalid. Correctthe format and continue. Refer to the BIM-ALERT/CICS Security Administrator'sGuide for information about valid FROM formats.

INVALID TO DATE ... RE-ENTER (GK161)The TO date entered on the DVIO, PVIO, or DAUD screen is invalid. Correct theformat and continue. Refer to the BIM-ALERT/CICS Security Administrator's Guidefor information about valid TO formats.

GK145

GK146

GK147

GK148

GK150

GK160

GK161



INVALID FROM TIME ... RE-ENTER (GK162)The FROM time entered on the DVIO, PVIO, or DAUD screen is invalid. Correctthe format and continue. Refer to the BIM-ALERT/CICS Security Administrator'sGuide for information about valid FROM formats.

INVALID TO TIME ... RE-ENTER (GK163)The TO time entered on the DVIO, PVIO, or DAUD screen is invalid. Correct theformat and continue. Refer to the BIM-ALERT/CICS Security Administrator's Guidefor information about valid TO formats.

TERMINAL-ID IS NOT SECURED ... RE-ENTER (GK164)The terminal ID specified on the DVIO or PVIO screen is not defined as a securedterminal, and therefore no violations can exist for it. If you are using dynamicterminal support, this message should never be issued.

USER ID IS NOT SECURED ... RE-ENTER (GK165)The user ID specified on the DVIO or PVIO screen as a search argument is notdefined in the security file and therefore cannot have any violations reported againstit.

ADMINISTRATOR NOT ON FILE ... RE-ENTER (GK166)The administrator user ID specified on the DVIO, PVIO, or DAUD screen as asearch argument is not defined in the security file, and therefore it cannot own anyoperators or terminals.

UNAUTHORIZED ADMINISTRATOR SPECIFIED ... RE-ENTER (GK167)Subadministrators are authorized to see only those violations committed by terminalsor operators they own. Any request to see violations committed by terminals oroperators owned by another administrator is denied.

NO SPECIFIED AUDIT RECORDS ON FILE (GK168)No audit records on file satisfy all the input arguments.

NO SPECIFIED VIOLATION ATTEMPTS ON FILE (GK168A)No violations have been logged that satisfy all the input arguments.

GK162

GK163

GK164

GK165

GK166

GK167

GK168

GK168



INVALID VIOLATION CODE SPECIFIED (GK169)The violation code specified is not valid. See page 3-71 for a list of the validviolation codes and the violations they denote.

INVALID FUNCTION SPECIFIED (GK170)The function specified on the DAUD selection panel is not a valid BIM-ALERTfunction. Specify a valid function to continue.

INVALID PRINTER-ID SPECIFIED ... RE-ENTER (GK170A)The printer specified on the Print Attempted Violations screen is not defined in theTCTTE as a printer.

PRINTER UNAVAILABLE FOR PRINTING (GK171)The printer specified on the Print Attempted Violations screen has been flagged inthe TCTTE as unavailable (out of service, etc.), and therefore the print requestcannot be honored.

INTERVAL CONTROL ERROR - EIBRCODE = X'XXXXXXXX' - XXXXXXXX(GK172)An abnormal return code was received in response to the interval control request tostart task S196 in order to print violations. The request cannot be honored. Refer topage 5-4 to determine the meaning of the interval control return code X'XXXXXXXX'.

ERROR ACCESSING SECURITY FILE S1SCTY - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK175)An error occurred during an attempt to access the security file. The program issuingthe message is identified by XXXXXXXX. Refer to page 5-3 for the meaning of thefile access return code X'XXXXXXXX'.

ERROR ACCESSING SECURITY LOG FILE S1SECLG - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK176)An error occurred during an attempt to access the log file. The program issuing themessage is identified by XXXXXXXX. Refer to page 5-3 for the meaning of the fileaccess return code X'XXXXXXXX'.

GK169

GK170

GK170

GK171

GK172

GK175

GK176



ERROR ACCESSING SECURITY FILE S1SAUDT - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK177)An error occurred during an attempt to access the audit file. The program issuing themessage is identified by XXXXXXXX. Refer to page 5-3 for the meaning of the fileaccess return code X'XXXXXXXX'.

CICS LOAD FAILURE - MODULE - XXXXXXXX - XXXXXXXX (GK178)An error occurred during an attempt to load the CICS module XXXXXXXX via CICSservices. Check that the program is cataloged in a library contained in the CICSstartup library search string and that it is included in the PPT in use by using thecommand CEMT INQ PROG(XXXXXXXX).

BIM-ALERT/CICS NOT INITIALIZED ... REQUEST DENIED (GK180)The requested function requires that BIM-ALERT/CICS be active in order to extractthe requested information. The request cannot be honored because BIM-ALERT/CICS is not active.

MORE UNSECURED VVVVVVVVVVVS ... PRESS ENTER - XXXXXXXX(GK181)There are more unsecured resources of type VVVVVVVVVVV defined in the CICStables. Press ENTER to see the next screen. XXXXXXXX identifies the programissuing the message.

MORE USERS TO REPORT ... PRESS ENTER - XXXXXXXX (GK181A)There are more users currently signed on to the system. Press ENTER to see thenext screen. XXXXXXXX identifies the program issuing the message.

VVVVVVVVVVV SECURITY NOT ACTIVATED - XXXXXXXX (GK182)A request has been made to list the unsecured resources of type VVVVVVVVVVV, butsecurity for that resource type has not been activated. XXXXXXXX identifies theprogram issuing the message.

END OF UNSECURED VVVVVVVVVVVS - XXXXXXXX (GK183)This is the last panel of unsecured resources (VVVVVVVVVVV) defined in thesystem. XXXXXXXX identifies the program issuing the message.

GK177

GK178

GK180

GK181

GK181

GK182

GK183



END OF USER REPORT - XXXXXXXX (GK183A)No more users are currently signed on to the system.

INTERNAL ERROR ON TCT LOCATE (GK184)The table lookup for a terminal has failed. The resource name is probably spelledincorrectly.

INVALID VVVVVVVVVVV TABLE ADDRESS (GK185)The address being used to locate the BIM-ALERT/CICS VVVVVVVVVVV table isinvalid. This indicates either an internal error in BIM-ALERT/CICS or a storageoverlay. Contact BIM Technical Support for assistance.

STARTING TERMINAL INVALID (GK186)The starting terminal ID specified on the USER panel cannot be found in the table.

NO TERMINALS TO REPORT UPON (GK187)No terminals have been found that match the search argument supplied on the USERpanel.

VERSION INFORMATION NOT FOUND (GK189)The version information cannot be located in the requested module. Either themodule selected is not a BIM-ALERT/CICS module or it is a map, which does notcontain version information.

CORRECTIVE ZAP INFORMATION NOT FOUND (GK191)The header for the corrective zap information cannot be located in the loadedmodule. This probably indicates a corrupted module. Contact BIM TechnicalSupport for assistance.

OPTIONAL ZAP INFORMATION NOT FOUND (GK192)The header for the optional zap information cannot be located in the loaded module.This probably indicates a corrupted module. Contact BIM Technical Support forassistance.

GK183

GK184

GK185

GK186

GK187

GK189

GK191

GK192



GETMAIN FAILURE - EIBRCODE = X'XXXXXXXX' - XXXXXXXX (GK193)An error has occurred during an attempt to acquire CICS storage. Refer to page 5-6for the meaning of the storage request return code X'XXXXXXXX'.

BIM-ALERT SERVER ERROR DETECTED - ERRORCODES=XXXXXXXXXX-XXXXXXXX (GK194)An error occurred during a call to the BIM-ALERT server. Contact BIM TechnicalSupport for assistance in resolving the problem.

GK193

GK194

Online File Maintenance Messages



The messages in the range of GK200 to GK249 are produced by the online filemaintenance programs. Where applicable, the name of the program issuing themessage is reported at the end of the message; it is denoted by XXXXXXXX.

ERROR ACCESSING SECURITY FILE S1SCTY - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK200)An error occurred while accessing the security file. Refer to page 5-3 for themeaning of the file access return code X'XXXXXXXX'.

ERROR ACCESSING SECURITY AUDIT FILE S1SAUDT - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK201)An error occurred during an attempt to access the audit file. Refer to page 5-3 forthe meaning of the file access return code X'XXXXXXXX'.

ERRORS DETECTED ... CORRECT/RE-ENTER - XXXXXXXX (GK202)Errors have been detected in the input data by one of the various editing routines.The fields in error are displayed in high intensity. Correct the input and continueprocessing.

INVALID VVVVVVVVVVV NAME(S) DETECTED ... RE-ENTER -XXXXXXXX (GK203)Subadministrators are permitted to assign to terminals or operators under theircontrol only those resources included in their own profiles. The type of resource thesubadministrator attempted to assign is identified by VVVVVVVVVVV.

INVALID BIM-ALERT TRANSACTION ... CORRECT/RE-ENTER -XXXXXXXX (GK203A)The BIM-ALERT transaction entered is not defined in the BIM-ALERT/CICSsecurity file. Either correct your input or add the transaction as a securedtransaction.

NO DESCRIPTION - XXXXXXXX (GK204)The descriptive information used for clarity in reporting must be entered when theresource is added. Add the descriptive information and continue.

Introduction

GK200

GK201

GK202

GK203

GK203

GK204



NAME MISSING (GK204A)The field name, which is used for clarity in reporting, must be entered when securityfor the map is defined. Add the descriptive name and continue.

TITLE MISSING (GK204B)The title name, which is used for clarity in reporting, must be entered when securityfor the map is defined. Add the descriptive title and continue.

VVVVVVVVVVV LIMIT EXCEEDED - BRIGHT VVVVVVVVVVV(S) NOTADDED - XXXXXXXX (GK205)The maximum number of resources of type VVVVVVVVVVV has been defined. Anyresource displayed in high intensity has not been added as a secured resource. Thelimits are 1600 transactions, 2000 programs, 800 files, and 2000 field-levelresources.

MAP LIMIT EXCEEDED - MAP NOT ADDED (GK205A)The maximum number of restricted map profiles (2000) has already been defined.Therefore, this map cannot be added as a restricted map.

VVVVVVVVVVV ALREADY ON SECURITY FILE - XXXXXXXX (GK206)You are attempting to add a resource of type VVVVVVVVVVV that has already beendefined. Use the update function to alter the resource's characteristics.

THIS VERSION OF MAP SECURITY ALREADY ON FILE WITH ASSIGNEDREF. # XXXXXXXX (GK207)You are attempting to define map restrictions that are already defined. Use theupdate function to alter existing definitions.

VVVVVVVVVVV(S) NOT ON FILE - XXXXXXXX (GK208)The resources displayed in high intensity are not defined as secured resources.Either correct your input or add the resources as secured resources.

ADMINISTRATOR NOT ON FILE - XXXXXXXX (GK208A)You are attempting to assign an operator or a terminal to an administrator who hasnot been to defined to BIM-ALERT/CICS.

GK204

GK204

GK205

GK205

GK206

GK207

GK208

GK208



DUPLICATE VVVVVVVVVVV(S) DETECTED ... RE-ENTER - XXXXXXXX(GK209)The same resource name has been entered on the screen more than once. Theduplicate entries are displayed in high intensity.

DUPLICATE FIELD NUMBERS DETECTED ... RE-ENTER - XXXXXXXX(GK209A)The same field number has been specified twice in the field definitions. Theduplicate entries are displayed in high intensity.

DUPLICATE BIM-ALERT TRANSACTIONS DETECTED ... CORRECT/RE-ENTER - XXXXXXXX (GK209B)The same transaction ID has been entered for more than one BIM-ALERTtransaction. The duplicate entries are displayed in high intensity.

DUPLICATE MAP NAME / REF. # DETECTED ... CORRECT/RE-ENTER -XXXXXXXX (GK209C)The same map name and reference number have been entered for more than onemap. The duplicate entries are displayed in high intensity.

DUPLICATE USERID VVVVVVVV FOUND IN XXXXXXXX USER PROFILERECORD (GK209D)The requested operation (add or update user profile) failed because one of thespecified user IDs matched a user ID in an existing user profile. XXXXXXXXindicates the existing user profile record. Specify a different user ID and try the addor update user profile operation again.

SYSTEM VVVVVVVVVV CODE ... CANNOT BE SECURED - XXXXXXXX(GK210)Certain internal resources used by CICS cannot be defined as secured resourcesbecause CICS may not be able to function properly if the resources are incorrectlyallocated.

NO VVVVVVVVVVV(S) ENTERED - XXXXXXXX (GK211)Required data (VVVVVVVVVVV) necessary to process the request has not beenentered. Enter the required data to continue processing.

GK209

GK209

GK209

GK209

GK209

GK210

GK211



NO MAP NAME ENTERED - XXXXXXXX (GK211A)A secured map cannot be added without a map name. Enter the required data tocontinue processing.

NO MAPSET NAME ENTERED - XXXXXXXX (GK211B)A secured map cannot be added without a mapset name. Enter the required data tocontinue processing. If the map was not defined with a mapset name, enter the mapname as the mapset name.

NO MAP FIELDS ENTERED - XXXXXXXX (GK211C)Map security cannot be defined without securing at least one field on the map. Enterthe required data to continue processing.

NO SCAN ARGUMENT ENTERED - XXXXXXXX (GK211D)A scan argument must be entered on the OPER or GRPS panel in order to extractuser IDs from the file. Enter the required data to continue processing.

NO NEW PASSWORD ENTERED - XXXXXXXX (GK211E)You must specify the password you want BIM-ALERT to assign to the operator asan expired password. Enter the required data to continue processing.

SPECIFIED MAP SET NAME NOT FOUND IN PROGRAM LIBRARY -XXXXXXXX (GK212)The mapset name entered has not been cataloged into any library in the CICS searchchain.

SPECIFIED MAP NAME NOT FOUND IN THE MAPSET - XXXXXXXX(GK213)The map name specified cannot be located in the specified map set. Make sure bothpieces of information are spelled correctly.

SPECIFIED MAP NAME IS NOT AN OUTPUT MAP TYPE - XXXXXXXX(GK214)The map security defined by the BIM-ALERT/CICS online panels affects onlyoutput maps. The map specified is not defined as an output map and thereforecannot be secured.

GK211

GK211

GK211

GK211

GK211

GK212

GK213

GK214



USER CLASS INCORRECTLY SPECIFIED - XXXXXXXX (GK216)You have specified a plus sign (+) as the first character of the name, which signifiesan administrator, but you have not defined the user class as an administrator (M, T,or O). Either change the user class to M, T, or O, or remove the plus sign (+) fromthe name.

INVALID SECURITY ADMINISTRATOR NAME ... RE-ENTER - XXXXXXXX(GK217)The operator you are attempting to add has an user class that signifies anadministrator, but the name is not in the administrator format. If you want to definean administrator, specify a plus sign as the first character of the name. Otherwise,change the user class to regular operator (R).

INCORRECT FUNCTION ENTERED ... CORRECT/RE-ENTER -XXXXXXXX (GK218)The response entered into the submenu at the bottom of the screen is not one of theacceptable choices. Enter one of the specified function codes to continue.

MAXIMUM ALERT TRANSACTION CODES EXCEEDED .. CORRECT/RE-ENTER - XXXXXXXX (GK219)A maximum of six ALERT transactions are permitted per operator or terminal.Those entered on the screen plus those already existing in the record will cause thetotal to be greater than six.

MODEL NOT ON FILE ... CORRECT/RE-ENTER - XXXXXXXX (GK220)The specified model could not be located in the file. Make sure the model name isspelled correctly and try again.

ADMINISTRATOR NOT ON FILE ... CORRECT/RE-ENTER - XXXXXXXX(GK220A)The specified administrator could not be located in the file. Make sure theadministrator name is spelled correctly and try again.

ADMINISTRATOR UNAUTHORIZED VVVVVVVVVVV(S) DETECTED -XXXXXXXX (GK221)Administrators are permitted to assign to terminals or operators only those resourcesthey themselves are permitted to use. The type of resource the administratorattempted to assign is identified by VVVVVVVVVVV.

GK216

GK217

GK218

GK219

GK220

GK220

GK221



VVVVVVVVVVV UPDATES COMPLETE - XXXXXXXX (GK225)The requested updates for resource type VVVVVVVVVVV have been completed.

MESSAGE UPDATES COMPLETE - XXXXXXXX (GK225A)The requested updates have been made to the message file.

ADMINISTRATOR UPDATES COMPLETE - XXXXXXXX (GK225B)The requested administrator reassignments (either permanent or temporary) havebeen completed.

OPERATOR UPDATES COMPLETED, SECID XXXXXXXX ADDED -XXXXXXXX (GK225C)The requested updates were made to the operator record. The specified SECID waswas not found in the ALERTXP security file, so the SECID was added.

If you meant to specify an existing SECID rather than add a new one, use the ALXPUSEC submenu to remove the SECID record that was added. Then use the UserProfile panel to update the operator record with the intended SECID.

VVVVVVVVVVV(S) ADDED TO FILE ... CONTINUE - XXXXXXXX (GK226)The information for resource type VVVVVVVVVVV has been added to the file.

MAP SECURITY FOR MAP XXXXXXXX ADDED TO FILE WITH ASSIGNEDREF. # XXXXXXXX (GK226A)The specified map has been added to the file and assigned reference numberXXXXXXXX.

OPERATOR ADDED TO FILE, SECID XXXXXXXX ADDED - XXXXXXXX(GK226B)The requested operator information was added to the S1SCTY file. The specifiedSECID was not found in the ALERTXP security file, so it was added.

If you meant to specify an existing SECID rather than add a new one, use the ALXPUSEC submenu to remove the SECID record that was added. Then use the UserProfile panel to update the operator record with the intended SECID.

GK225

GK225

GK225

GK225

GK226

GK226

GK226



OPERATOR ADDED TO FILE, USERID/PASSWORD ALREADY EXISTS -XXXXXXXX (GK226C)The requested operator information was added to the S1SCTY file. A non-CICSuser ID and password already existed in the file, but BIM-ALERT completed the addoperation retaining the existing user ID and password information in the user profile.

END OF VVVVVVVVVVVS ON FILE - XXXXXXXX (GK227)The end of the resource type VVVVVVVVVVV has been reached during a browseoperation or a display of terminal and operator resources.

MORE VERSIONS OF SECURITY ON FILE FOR MAP XXXXXXXX ...PRESS PF-8 - XXXXXXXX (GK228)There are additional security profiles defined for map XXXXXXXX.

VVVVVVVVVVV VVVVVVVVVVV DELETIONS COMPLETED - XXXXXXXX(GK229)The specified resources of type VVVVVVVVVVV have been removed from theterminal or operator's profile as requested.

VVVVVVVVV NAME AND PROCESS UPDATES COMPLETED -XXXXXXXX (GK229A)The requested process updates have been made to the file.

VVVVVVVVVVV VVVVVVVVVVV(S) ADDED TO FILE - XXXXXXXX(GK230)The specified resources of type VVVVVVVVVVV have been added to the terminal oroperator's profile as requested.

OPERATOR SPECIFIED NOT AN ADMINISTRATOR . CORRECT/RE-ENTER - XXXXXXXX (GK231)The operator to whom you are attempting to assign a terminal or operator is notdefined as an administrator.

ERROR ACCESSING SECURITY FILE XXXXXXXX - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK232)An error occurred during an attempt to access the specified file. Refer to page 5-3for the meaning of the file access return code X'XXXXXXXX'.

GK226

GK227

GK228

GK229

GK229

GK230

GK231

GK232



LOGICAL CONNECTOR (AND/OR) NOT SPECIFIED (GK233)You have attempted to add additional segments to an existing field-level resourcedefinition, but have not specified the connector AND or OR.

STORAGE FAILURE - EIBRCODE = X'XXXXXXXX' - XXXXXXXX (GK234)The requested operation (add or update user profile) failed because the programcould not obtain the storage required. Refer to page 5-6 for the meaning of thestorage request return code X’XXXXXXXX.

GK233

GK234

Activation and Deactivation Messages



The messages in the range of GK250 to GK299 are produced by the programs thatactivate or deactivate resources. The name of the program issuing the messageappears at the end of the message and is denoted by XXXXXXXX.

ERROR ACCESSING SECURITY FILE S1SCTY - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK250)An error occurred during an attempt to access the security file. Refer to page 5-3 forthe meaning of the file access return code X'XXXXXXXX'.

ERROR ACCESSING SECURITY FILE S1SAUDT - EIBRCODE =X'XXXXXXXX' - XXXXXXXX (GK251)An error occurred during an attempt to access the audit file. Refer to page 5-3 forthe meaning of the file access return code X'XXXXXXXX'.

SECURITY INACTIVE ... REQUEST DENIED - XXXXXXXX (GK255)It is not possible to activate any resource when BIM-ALERT/CICS is not active.

VVVVVVVVVVV SECURITY INACTIVE ... REQUEST DENIED - XXXXXXXX(GK256)It is not possible to activate any resource of type VVVVVVVVVVV because securityfor that resource type has not been activated.

VVVVVVVVVVV CAPACITY EXCEEDED ... REQUEST DENIED -XXXXXXXX (GK257)The security table for resource type VVVVVVVVVVV is full. No new entries can beactivated until the security table is refreshed.

VVVVVVVVVVV EXCEEDS CURRENT LIMITS - XXXXXXXX (GK258)This resource cannot be activated because its reference number would put it beyondthe limits of the current table. The resource cannot be secured until the security tableis refreshed.

Introduction

GK250

GK251

GK255

GK256

GK257

GK258



INVALID VVVVVVVVVVV ... RE-ENTER - XXXXXXXX (GK259)The resource you are attempting to activate cannot be located in the security file.Check the spelling and the case and try again.

INVALID MAP NAME OR REF. NUMBER .. RE-ENTER - XXXXXXXX(GK259A)The map you are attempting to activate cannot be located in the security file. Eitherthe map name or the reference number is incorrect. Correct and reenter theinformation.

INVALID MAP NAME .. RE-ENTER - XXXXXXXX (GK259B)The map you are attempting to activate cannot be located in the security file becausethe map name is invalid. Correct and reenter the information.

INVALID REF. NUMBER .. RE-ENTER - XXXXXXXX (GK259C)The map you are attempting to activate cannot be located in the security file becausethe reference number is invalid. Correct and reenter the information.

TERMINAL-ID XXXXXXXX NOT FOUND - XXXXXXXX (GK261)The terminal ID XXXXXXXX could not be located in the TCTTE. The operator isactivated normally to BIM-ALERT/CICS, but his or her operator information couldnot be cleared from the TCTTE.

ACTIVATION COMPLETE ... CONTINUE - XXXXXXXX (GK270)The requested resource has been activated successfully. If it was already secured,any update made to that resource's profile is now in effect. If it was previouslyunsecured, the resource is now secured.

DEACTIVATION COMPLETE ... CONTINUE - XXXXXXXX (GK271)The requested resource has been deactivated successfully. No access to the resourcewill be prohibited by BIM-ALERT/CICS unless the resource is reactivated.

XXXXXXXX SUCCESSFULLY REFRESHED - XXXXXXXX (GK281)The monitor, exit, or logo XXXXXXXX has been successfully refreshed and thechanges made to it are now in effect.

GK259

GK259

GK259

GK259

GK261

GK270

GK271

GK281



MODULE NOT REFRESHED - NOT CURRENTLY ACTIVE -XXXXXXXX(GK282)The monitor, exit, or logo cannot be refreshed because the resource is not currentlyloaded and therefore there is nothing to refresh.

STORAGE FAILURE - RETURN CODE = XXXXXXXX - XXXXXXXX(GK283)The new monitor, exit, or logo could not be loaded due to a storage failure. Refer topage 5-6 for the meaning of the storage request return code X'XXXXXXXX'.

LOAD FAILURE - RETURN CODE = XXXXXXXX - XXXXXXXX (GK284)The new monitor, exit, or logo could not be loaded due to a load failure. Refer topage 5-6 for the meaning of the load request return code X'XXXXXXXX'.

MODULE XXXXXXXX RESIDES IN SHARED STORAGE AND NOTREFRESHABLE - XXXXXXXX (GK285)Monitors, exits, and logos that have been loaded into shared storage cannot berefreshed.

MODULE XXXXXXXX IS NOT A VALID BIM-ALERT/CICS LOGO MODULE- XXXXXXXX (GK286)The logo module XXXXXXXX is not in the BIM-ALERT/CICS logo format andtherefore cannot be refreshed.

GK282

GK283

GK284

GK285

GK286

Sign-on and Sign-off Messages



The messages in the range of GK300 to GK400 are produced by the various modulesinvolved in terminal and operator sign-on and sign-off processing. Where applicable,the message contains the identifier of the module issuing the message, denoted byXXXXXXX.

SIGN-ON IS COMPLETE - ENTER NEXT TRANSACTION - XXXXXXXX(GK300)The sign-on process has completed normally; the operator may proceed with normalprocessing.

SIGN-OFF IS COMPLETE - XXXXXXXX (GK301)The sign-off process has completed normally.

YOUR PASSWORD EXPIRES IN XXXXXXXX DAYS - XXXXXXXX (GK302)This message is issued at sign-on completion beginning 15 days prior to theexpiration of a password. The operator should change the code prior to expiration.

LAST SIGN-ON FROM TERMINAL XXXXXXXX ON XXXXXXXX ATXXXXXXXX (GK303)This message is issued at operator sign-on completion to let the operator know ifsomeone else has signed on with his or her profile.

LAST SIGN-ON DATA NOT AVAILABLE (GK304)This operator has never signed on to the BIM-ALERT/CICS system and therefore noprevious sign-on information is stored in the profile.

PASSWORD UPDATE COMPLETE - XXXXXXXX (GK305)The operator or terminal password has been changed as requested.

TERMINAL ID ERROR ... RE-ENTER (GK310)The terminal ID entered on the Terminal Sign-on screen is not really the terminalthat the user is attempting to sign on to.

Introduction

GK300

GK301

GK302

GK303

GK304

GK305

GK310



PASSWORD ERROR ... RE-ENTER (GK311)The password entered on the Terminal Sign-on screen does not match the passworddefined in the file for that terminal. Carefully reenter the password and try again.

USER ID ERROR ... RE-ENTER (GK312)The user ID entered on the Operator Sign-on screen could not be located in the file.Carefully reenter the user ID and try again.

NAME ERROR ... RE-ENTER (GK313)The name entered on the Operator Sign-on screen does not match the name definedfor that operator in the security file. Carefully reenter the name and try again.

PASSWORD ERROR ... RE-ENTER (GK314)The password entered on the Operator Sign-on screen does not match the passworddefined in the file for that operator. Carefully reenter the password and try again.

PASSWORD ERROR .. RE-ENTER, RETURN CODE = X'XXXXXXXX' -EXTERNAL SECURITY (GK314A)The password entered has failed both the BIM-ALERT/CICS validation and theexternal security product validation tests. Carefully reenter the password and tryagain. The following are possible return code values:

Code Meaning

01 The user ID was not found in CA-ALERT for VM database.

06 The value supplied for the CA-ALERT for VM password is invalid.

For information about valid password values, see the BIM-ALERT/CICSSecurity Administrator’s Guide.

07 The operator is not authorized to change his own CA-ALERT for VMpassword.

10 The CA-ALERT for VM user exit denied the password change request.

11 The new password matches a previously used CA-ALERT for VM password.

13 The new password does not match the CA-ALERT for VM password mask.

14 The new password matches the user ID.

17 The minimum CA-ALERT for VM password keep time was not met.

18 The new password is contained in the CA-ALERT for VM restricted list.

19 The new password failed the CA-ALERT for VM character repetition check.

GK311

GK312

GK313

GK314

GK314



NEW PASSWORD MATCHES EXISTING PASSWORD - UPDATEIGNORED - XXXXXXXX (GK320)The new password entered matches a password stored in the password history recordand cannot be used again. The password is not changed.

NEW PASSWORD CHECK FAILURE - XXXXXXXX (GK321)The new password and new password-check data entered on the screen must matchbefore the new password can be considered for validation. This is to prevent theoperator from mistakenly entering data in a dark field.

NEW GROUP PASSWORD IGNORED - XXXXXXXX (GK322)The new password entered cannot be changed because the operator is part of agroup. If one member of the group were allowed to change the password, no oneelse would be able to sign on.

XXXXXXXX FORMAT ERROR - PASSWORD UPDATE IGNORED -XXXXXXXX (GK323)The new password must match the format XXXXXXXX to be valid. Sign on againand type a password in the specified format in order to change your password.

XXXXXXXX VOWEL ERROR - PASSWORD UPDATE IGNORED -XXXXXXXX (GK324)The password mask disallows vowels anywhere in the password. Sign on again andtype a valid password in order to change your password.

"HELP" INVALID AS PASSWORD - UPDATE IGNORED - XXXXXXXX(GK325)The word help (in either upper or lower case) is not valid as a password.

SECURITY FILE OPENED READONLY - UPDATE IGNORED - XXXXXXXX(GK326)The security file is defined as read-only in the system from which you are attemptingto change your password; therefore, your attempt to update it was disallowed. Tochange your password, you must sign on to the system where the file is defined asread/write.

GK320

GK321

GK322

GK323

GK324

GK325

GK326



PASSWORD EXPIRED - S1SCTY FILE READONLY - LOGONIMPOSSIBLE - XXXXXXXX (GK327)Your password has expired, but the BIM-ALERT/CICS system cannot change itbecause the file cannot be updated from this CICS system. Sign on to the system onwhich the file is defined as read/write to change your password or to have the BIM-ALERT/CICS system issue you a new one.

PASSWORD EXPIRED - PLEASE CHANGE IT TO SIGN ON - XXXXXXXX(GK328)Your password has expired, but the administrator has disabled the automaticpassword generation function of BIM-ALERT/CICS. You must sign on again andsupply a new password in order to sign on to the system.

UNAUTHORIZED TERMINAL ... SYSTEM ACCESS PROHIBITED (GK330)The operator is attempting to sign on to a terminal for which she or he is notauthorized. An operator may sign on to only those terminals that either are listed asprimary or alternate terminals in the operator's profile, or are authorized for a groupto which the operator belongs.

OPERATOR ALREADY SIGNED ON ... SIGN-ON DENIED (GK331)A non-group operator is trying to sign on to BIM-ALERT/CICS but is already signedon elsewhere. Try again to sign on, and enter a Y in the Reconnect field on the Sign-on screen. This instructs BIM-ALERT/CICS to sign you off the terminal you arecurrently signed on to in order to allow you to sign on at the new terminal.

xxxxxxxx SECURITY RECORD ERROR - EIBRCODE = X'XXXXXXXX' -XXXXXXXX (GK335)File control has returned an error code as a response to a file access. Refer to page5-3 for the meaning of the file access return code X'XXXXXXXX'.

LOAD FAILURE - RETURN CODE = XXXXXXXX MODULE = XXXXXXXX(GK336)The module XXXXXXXX could not be loaded for reason XXXXXXXX. Refer to page5-6 for the meaning of the load request return code X'XXXXXXXX'.

GK327

GK328

GK330

GK331

GK335

GK336



LOGO ==> XXXXXXXX NOT FOUND IN LIBRARY - BYPASSED -XXXXXXXX (GK337)The logo specified on UTOP could not be located. This logo may also have a suffixappended to it from the Terminal Profile screen. Ensure that a logo of the nameXXXXXXXX has been cataloged into a library that is available to CICS.

MODULE ==> XXXXXXXX IS NOT A LOGO - BYPASSED - XXXXXXXX(GK338)The module defined as the logo to move to the screen at sign-on time has beenlocated in a library but is not in the format of a BIM-ALERT/CICS logo. Ensure thatthe module name is correct and that the logo assembled and linked properly.

TEMPORARY STORAGE ERROR - EIBRCODE = X'XXXXXXXX' -XXXXXXXX (GK339)A non-zero return code was returned in response to a temporary storage request.Refer to page 5-6 for the meaning of the load request return code X'XXXXXXXX'.

NEW PASSWORD IS INVALID, RETURN CODE = X'XXXXXXXX' -EXTERNAL SECURITY (GK340)The external security product has disallowed the new password for the reasonspecified by X’XXXXXXXX’. Try a different new password. The following arepossible return code values:

Code Meaning






11 The new password matches a previously used CA-ALERT for VM password.

13 The new password does not match the CA-ALERT for VM password mask.




19 The new password failed the CA-ALERT for VM character repetition check.

GK337

GK338

GK339

GK340

Batch/Utility Program Messages



The messages in the range of GK500 to GK699 are produced by the batch or batchutility programs supplied with BIM-ALERT/CICS.

ERROR OPENING SECURITY FILE S1SCTY - RC = XXXXXXXX EC =XXXXXXXX - XXXXXXXX (GK500)An error occurred during an attempt to open the security file. The VSAM returncode (RC) and error code (EC) are displayed. Refer to the IBM publicationVSE/VSAM Messages and Codes for the meanings of the return and error codes.

ERROR OPENING SECURITY AUDIT FILE S1SAUDT - RC = XXXXXXXXEC = XXXXXXXX - XXXXXXXX (GK501)An error occurred during an attempt to open the security audit file. The VSAMreturn code and error code are displayed. Refer to the IBM publication VSE/VSAMMessages and Codes for the meanings of the return and error codes.

ERROR OPENING SECURITY FILE S1SECLG - RC = XXXXXXXX EC =XXXXXXXX - XXXXXXXX (GK502)An error occurred during an attempt to open the security log file. The VSAM returncode and error code are displayed. Refer to the IBM publication VSE/VSAMMessages and Codes for the meanings of the return and error codes.

ERROR ACCESSING SECURITY FILE S1SCTY - RC = XXXXXXXX EC =XXXXXXXX - XXXXXXXX (GK505)An error occurred during an attempt to access the Security file. The VSAM returncode and error code are displayed. Refer to the IBM publication VSE/VSAMMessages and Codes for the meanings of the return and error codes.

ERROR ACCESSING SECURITY AUDIT FILE S1SAUDT - RC =XXXXXXXX EC = XXXXXXXXX (GK506)An error occurred during an attempt to access the Security Audit file. The VSAMreturn code and error code are displayed. Please refer to the IBM publicationVSE/VSAM Messages and Codes for the meanings of the return and error codes.

Introduction

GK500

GK501

GK502

GK505

GK506



ERROR ACCESSING SECURITY FILE S1SECLG - RC = XXXXXXXX EC =XXXXXXXX (GK507)An error occurred during an attempt to access the Security Log file. The VSAMreturn code and error code are displayed. Refer to the IBM publication VSE/VSAMMessages and Codes for the meanings of the return and error codes.

EXEC PARM MISSING OR INVALID - S1C009 (GK508)A valid EXEC PARM is required for the S1C009 program. For information aboutthe content of the EXEC PARM, see the BIM-ALERT/VSE and CICS-VSEInstallation and Operations Guide.

NO USER PROFILES FOUND IN TABLE xx (GK508A)The table you specified with the ALTV= EXEC parameter does not contain any userprofile records to convert. Restart the conversion process and specify the correcttable number.

USER PROFILE DATA NOT COMPLETELY CONVERTED (GK509)The conversion program could not convert some BIM-ALERT/VSE user profile datato the 4.9 format. For detailed information about what data was not converted, seethe warning messages displayed on the printer.

S1SCTY FILE ERROR - XXXXXXXX CONTROL RECORD NOT FOUND(GK515)BIM-ALERT could not find the control record required for the conversion process.This indicates the input security file has been corrupted. Restore a backup file andrestart the conversion process.

CONTROL RECORD ERROR ON VVVVVVVVVVV RECORD (GK516)An error was encountered during an attempt to read the control record for resourcetype VVVVVVVVVVV from the security file. The job is terminated.

INTERNAL ERROR - PLEASE CONTACT BIM TECHNICAL SUPPORT.(GK517)This message will always follow a critical error message such as GK516. ContactBIM Technical Support for assistance.

GK507

GK508

GK508

GK509

GK515

GK516

GK517



NO VVVVVVVVVVV RECORDS IN SECURITY FILE (GK518)There are no records of resource type VVVVVVVVVVV defined in the S1SCTY file.

OPERATOR BATCH UTILITIES NOT AUTHORIZED AT THIS TIME <-*-*-*-*(GK530)Operator reports and utilities can be run only when authorized by a securityadministrator via the UTOP transaction. The control field is reset at successful end-of-job to prevent any unauthorized person from running the report. Refer to thefields on the UTOP screen to permit the report to be run.

OPERATOR BATCH UTILITIES AUTHORIZATION HAS EXPIRED <-*-*-*-*(GK531)The operator reports have an expiration feature that prevents a report from beingauthorized too far in advance. The batch report must be run by midnight of the datethe report was authorized.

TERMINAL BATCH UTILITIES NOT AUTHORIZED AT THIS TIME <-*-*-*-*(GK532)The terminal batch utility can be run only when authorized by a securityadministrator via the UTOP transaction. The control field is reset at successful end-of-job to prevent any unauthorized person from running the utility. Refer to thefields on the UTOP screen to permit the utility to be run.

TERMINAL BATCH UTILITIES AUTHORIZATION HAS EXPIRED <-*-*-*-*(GK533)The terminal batch utility has an expiration feature that prevents it from beingauthorized too far in advance. The batch utility must be run by midnight of the datethe report was authorized.

CONTROL CARD INPUT (GK540)This message indicates that control cards are being read.

END OF CONTROL CARD INPUT (GK541)This message indicates that control cards have been read.

GK518

GK530

GK531

GK532

GK533

GK540

GK541



TOTAL INPUT TRANSACTIONS - XXXXXXXX (GK542)This message is issued by S1U560 after all input cards have been read. XXXXXXXXis the number of cards read minus the number of comment cards.

TOTAL VALID TRANSACTIONS PROCESSED - XXXXXXXX (GK543)XXXXXXXX indicates the total number of valid transactions that were processed.

TOTAL TRANSACTIONS IN ERROR - XXXXXXXX (GK544)XXXXXXXX indicates the total number of transactions that were in error.

TOTAL TRANSACTIONS PROCESSED - XXXXXXXX (GK545)XXXXXXXX indicates the total number of transactions, both valid and invalid, thatwere processed.

START OF CONTROL CARD EDIT (GK546)This message indicates that control card editing has begun.

END OF CONTROL CARD EDIT (GK547)This message indicates that control card editing has ended.

VVVVVVVVVVV XXXXXXXX ADDED TO XXXXXXXX VVVVVVVVVVV(S)AND XXXXXXXX MODEL(S) (GK548)Resource XXXXXXXX of resource type VVVVVVVVVVV was added to the profiles ofthe specified number (XXXXXXXX) of operators, terminals, or groups(VVVVVVVVVVV), and to the profiles of the specified number (XXXXXXXX) ofmodels.

VVVVVVVVVVV XXXXXXXX ADDED TO XXXXXXXX VVVVVVVVVVV(S)(GK548A)Resource XXXXXXXX of resource type VVVVVVVVVVV was added to the profiles ofthe specified number (XXXXXXXX) of operators, terminals, or groups(VVVVVVVVVVV).

GK542

GK543

GK544

GK545

GK546

GK547

GK548

GK548



VVVVVVVVVVV XXXXXXXX DELETED FROM XXXXXXXXVVVVVVVVVVV(S) AND XXXXXXXX MODEL(S) (GK548B)Resource XXXXXXXX of resource type VVVVVVVVVVV was deleted from theprofiles of the specified number (XXXXXXXX) of operators, terminals, or groups(VVVVVVVVVVV), and from the profiles of the specified number (XXXXXXXX) ofmodels.

VVVVVVVVVVV XXXXXXXX DELETED FROM XXXXXXXXVVVVVVVVVVV(S) (GK548C)Resource XXXXXXXX of resource type VVVVVVVVVVV was deleted from theprofiles of the specified number (XXXXXXXX) of operators, terminals, or groups(VVVVVVVVVVV).

TOTAL MODULES ON RELEASE TAPE - XXXXXXXX (GK549)XXXXXXXX indicates the total number of BIM-ALERT/CICS modules on the releasetape.

VVVVVVVVVVV AREA CLEARED IN XXXXXXXX - TABLE STORAGE NOTFREED DUE TO INVALID POINTER (GK550)An error occurred with a BIM-ALERT/CICS internal table pointer. The tablestorage could not be freed, but the control information was cleared and processingdid continue. This allows the BIM-ALERT/CICS tables to be reinitialized.

XXXXXXXX TABLE DATED XXXXXXXX NOW FREED (GK551)The storage occupied by the security table identified has been successfully freed byS1U010.

BIM-ALERT/CICS SHARED TABLES NOW FREED (GK552)This message indicates that the BIM-ALERT/CICS tables that were shared bymultiple CICS regions have been freed.

INVALID REPORT TYPE REQUESTED (GK554)The report type specified to S1B190 was not a valid report type (SPEC, ADMN,etc.).

NO VIOLATION CRITERIA SPECIFIED (GK555)No input was supplied to S1B192 in order to produce the violation report.

GK548

GK548

GK549

GK550

GK551

GK552

GK554

GK555



NO SPECIFIED VIOLATION ATTEMPTS ON FILE (GK556)No violations were found that meet the specifications supplied on the inputparameters.

END OF ATTEMPTED VIOLATIONS REQUESTED (GK557)The violation report has successfully completed.

PARAMETER CARDS ACCEPTED (GK558)The parameter cards submitted by the user have been validated and accepted.Processing continues.

AUDIT FILE RECORDS READ - XXXXXXXX (GK559)XXXXXXXX indicates the total number of records, excluding control cards, read fromthe BIM-ALERT/CICS audit file.

AUDIT FILE RECORDS PREVIOUSLY ARCHIVED - XXXXXXXX (GK560)XXXXXXXX indicates the total number of records in the audit file that have alreadybeen included on an archive backup tape.

ARCHIVE INPUT RECORDS READ - XXXXXXXX (GK561)XXXXXXXX indicates the total number of input records moved from the currentarchive backup to the new archive backup.

ARCHIVE OUTPUT RECORDS WRITTEN - XXXXXXXX (GK562)XXXXXXXX indicates the total number of records written to the new archive file,which is the number of records from an old archive file plus the number of newrecords from the audit file.

NO RECORDS SELECTED FROM INPUT FILE (GK563)No records in the input file satisfied the input selection criteria. Correct the criteriaand rerun the job.

XXXXXXXX RECORDS PASSED TO SORT PROGRAM (GK564)XXXXXXXX indicates the total number of records passed to be sorted in order toproduce the requested report.

GK556

GK557

GK558

GK559

GK560

GK561

GK562

GK563

GK564



ALL VVVVVVVVVVVS AUTHORIZED (GK565)All resources of resource type VVVVVVVVVVV are authorized for this operator orterminal.

NO MAP RESTRICTIONS ASSIGNED (GK566)There are no map restrictions assigned to this terminal or operator.

NUMBER OF TERMINALS NOT NUMERIC - DEFAULT 1000 TERMINALSUSED (GK567)The TERMINALS=XXXXXXXX parameter is not numeric. The specified parameteris ignored and the default of 1000 is used.

TERMINALS= PARAMETER OMITTED - DEFAULT 1000 TERMINALSUSED (GK568)A TERMINALS=XXXXXXXX parameter has been included in the input, but no valuewas coded. The default of 1000 terminals is used.

UPDATE PARM INVALID - DEFAULT TO 'MIXED' (GK569)The parameter in the UPDATE= statement was not OPERATOR, TERMINAL, orMIXED. Processing continues with the default parameter MIXED.

XXXXXXXX PARM INVALID - DEFAULTS USED (GK570)The parameter specified for the XXXXXXXX= keyword is invalid. The parameterspecified is ignored and processing continues using the default value.

XXXXXXXX KEYWORD OMITTED - DEFAULTS USED (GK571)The parameter specified for the XXXXXXXX= keyword is invalid. The parameterspecified is ignored and processing continues using the default value.

XXXXXXXX PARM INVALID - JOB TERMINATED (GK572)The parameter specified for the XXXXXXXX= keyword is invalid. The job isterminated.

XXXXXXXX KEYWORD OMITTED - JOB TERMINATED' (GK573)The XXXXXXXX= keyword, which is required, was omitted. The job is terminated.

GK565

GK566

GK567

GK568

GK569

GK570

GK571

GK572

GK573



UPDATE KEYWORD OMITTED - DEFAULT TO ALL (GK574)No UPDATE= keyword is coded in the program input. The default of ALL is used.

AFFECTS KEYWORD OMITTED - DEFAULT TO OPERATOR (GK575)No AFFECTS= keyword is coded in the program input. The default of OPERATORis used.

TYPOPER KEYWORD OMITTED - DEFAULT TO ADD (GK576)No TYPOPER= keyword is coded in the program input. The default of ADD isused.

FILE ACCESS MODE INVALID - DEFAULT TO INQUIRY (GK577)The file access mode parameter specified is not I or U. The parameter specified isignored and processing continues using the default of I.

SUBSYSTEM XXXXXXXX REPLACED WITH XXXXXXXX (GK578)Subsystem ID name XXXXXXXX was successfully changed to XXXXXXXX.

NO LOCATION RECORDS FOUND (GK579)The location records specified in the operator profile could not be found in the file.Processing continues.

VVVVVVVVVVV RECORD SUCCESSFULLY INITIALIZED (GK580)The record type VVVVVVVVVVV has been initialized successfully.

SECURITY FILE XXXXXXXX INITIALIZATION COMPLETE (GK581)File XXXXXXXX has been successfully initialized.

SECURITY FILE S1SCTY REORGANIZATION (STEP ONE) COMPLETE(GK581A)The security file has successfully undergone the first step (S1U001) of thereorganization process.

GK574

GK575

GK576

GK577

GK578

GK579

GK580

GK581

GK581



SECURITY FILE S1SCTY REORGANIZATION (STEP TWO) COMPLETE(GK581B)The security file has successfully undergone the second step (S1U002) of thereorganization process.

SECURITY FILE S1SCTY CONVERSION COMPLETED SUCCESSFULLY(GK581C)The 4.8 S1SCTY file has been successfully converted to the 4.9 format.

RECORDS READ: XXXXXXXX RECORDS DELETED: XXXXXXXXRECORDS WRITTEN: XXXXXXXX (GK582)The security file reorganization has completed successfully; the results are reportedin this message.

SECURITY FILE ALREADY IN CONVERTED FORMAT - CONVERSIONBYPASSED (GK583)The file conversion is unnecessary because the file is already in the correct format.

SCTY48 FILE IS NOT VERSION 04.08 (GK583A)The input file found is not in version 4.8 format. The version 4.9 file conversionprocess requires a version 4.8 input file.

Convert the input file to version 4.8. For instructions, see the BIM-ALERTInstallation and Operations Guide.

SCTY49 FILE ALREADY PARTIALLY CONVERTED TO 4.09 FORMAT(GK583B)The conversion was previously run on the output file, but the process was notcompleted.

Reinitialize the output file and start the conversion process again. For instructions,see the BIM-ALERT Installation and Operations Guide.

SCTY49 FILE PREVIOUSLY CONVERTED (GK583C)The conversion was previously run on the output file, and the process completed.

If you need to run the conversion again, reinitialize the version 4.9 output file and re-start the conversion process. For instructions, see the BIM-ALERT Installation andOperations Guide.

GK581

GK581

GK582

GK583

GK583

GK583

GK583



WARNING!

Any data present in the version 4.9 output file is lost when you reinitialize it.

SCTY49 FILE IS NOT VERSION 04.09 (GK583D)The output file found is not in version 4.9 format. Reinitialize the output file.

SCTY49 FILE NOT EMPTY (GK583E)The output file contains records not created by program S1U000.

Initialize a version 4.9 output file. Re-run the conversion program. For instructions,see the BIM-ALERT Installation and Operations Guide.WARNING!

Any data present in the version 4.9 output file is lost when you reinitialize it.

ALERTXP FILE IS NOT VERSION 4.08 (GK583F)The input ALERTXP file is not in version 4.8 format. Conversion of the 4.8 BIM-ALERT/VSE user profile information requires a version 4.8 ALERTXP file forinput.

Convert the input file to version 4.8. For instructions, see the BIM-ALERTInstallation and Operations Guide.

USING CONTROL SUFFIX ====> XXXXXXXX (GK584)This informational message is issued by the PLT shutdown program to inform youwhich control suffix is in use.

SUFFIX XXXXXXXX COUNTER CHANGED FROM XXXXXXXX TOXXXXXXXX (GK585)This informational message is issued by the PLT shutdown program to inform youthat the counter in the shared table has successfully been decremented.

SECURITY FILE S1SCTY CONVERSION FAILED (GK586)The S1SCTY file was not converted. For specific reasons why the conversion failed,see the messages displayed on the printer.

GK583

GK583

GK583

GK584

GK585

GK586



MAPNAME & REFERENCE # MUST BE ENCLOSED IN () (GK599)The map name and the map reference number must be enclosed in parentheses.Correct and reenter the information.

USER= PARAMETER MUST BE OPERATOR OR TERMINAL (GK600)An illegal parameter was specified for the USER= keyword. Specify OPERATORor TERMINAL and rerun the job.

RESOURCE= PARAMETER MUST BE TRANSACTIONS, PROGRAMS,FILES, OR MAPS (GK601)An illegal parameter was specified for the RESOURCE= keyword. SpecifyTRANSACTIONS, PROGRAMS, FILES, MAPS, or FIELDS and rerun the job.

XXXXXXXX IS NOT A SECURED RESOURCE (GK602)The resource XXXXXXXX was not added to BIM-ALERT/CICS as a secured resourceat the system level.

XXXXXXXX REF # XXXXXXXX IS NOT A SECURED MAP (GK603)The map XXXXXXXX with the reference number XXXXXXXX was not added to BIM-ALERT/CICS at the system level.

REFERENCE NUMBER NOT NUMERIC (GK604)Map reference numbers must be numeric. Correct the reference number and rerunthe job.

NO MATCHING TERMINAL-ID IN SECURITY FILE (GK605)The original terminal ID coded on the input card does not exist in the BIM-ALERT/CICS security file. The error is flagged in the in-core processing table andprocessing continues.

CODE 01 - ORIGINAL TERMINAL-ID GREATER THAN 4 CHARACTERS(GK606)The original terminal ID cannot exceed four characters in length. Correct theterminal ID and rerun the job.

GK599

GK600

GK601

GK602

GK603

GK604

GK605

GK606



CODE 02 - NEW TERMINAL-ID GREATER THAN 4 CHARACTERS(GK607)The new terminal ID cannot exceed four characters in length. Correct the terminalID and rerun the job.

CODE 03 - ORIGINAL RECORD STATUS GREATER THAN 1CHARACTER (GK608)The original record status cannot exceed one character in length. Correct the statusand rerun the job.

CODE 04 - ORIGINAL RECORD STATUS MUST BE A, D, P, E, OR K(GK609)The original record status must be A, D, P, E, or K. Correct the status and rerun thejob.

CODE 05 - NEW RECORD STATUS GREATER THAN 1 CHARACTER(GK610)The new record status cannot exceed one character in length. Correct the status andrerun the job.

CODE 06 - NEW RECORD STATUS MUST BE A, D, P, OR K (GK611)The new record status must be A, D, P, or K. Correct the status and rerun the job.

PREVIOUS ERROR DETECTED - RECORD NOT PROCESSED (GK612)An error in the in-core table for this entry was flagged by the edit routine. The entryis not processed. See the listing for the edit portion of the job to determine the exacterror.

SEVERE ERROR DETECTED - UPDATE NOT COMPLETED (GK613)A severe error has made it impossible to complete the job normally. This message isalways preceded by at least one message describing the reason or reasons why thejob had to be terminated prior to completion.

TIME= PARAMETER MUST BE TERMINAL OR OPERATOR (GK615)The TIME= parameter was neither TERMINAL nor OPERATOR. Processing isterminated. Correct the parameter and rerun the job.

GK607

GK608

GK609

GK610

GK611

GK612

GK613

GK614



ACCESS TIMES MUST BE NUMERIC (GK615)The specified access time is not numeric. Specify a numeric time and rerun the job.

REFERENCE NUMBER NOT NUMERIC - CARD NOT PROCESSED(GK615A)The map reference number is not numeric. Specify a numeric reference number andrerun the job.

DAY OF WEEK INVALID (GK616)The DAY= parameter specified is invalid. Specify a valid day of the week(MONDAY, TUESDAY, and so on), then rerun the job.

VVVVVVVVVVV TOO LONG - CARD NOT PROCESSED (GK617)A resource type (VVVVVVVVVVV) was specified that exceeds the maximum lengthallowed. The input card is ignored and processing continues.

REFERENCE NUMBER TOO LONG - CARD NOT PROCESSED (GK617A)The map reference number specified is longer than four characters. Correct thereference number and rerun the job.

VVVVVVVVVVV NOT SECURED - NOT PROCESSED (GK618)A transaction, program, or file name (VVVVVVVVVVV) was specified that is not asecured resource and that therefore cannot be added to an operator or terminalprofile. The input card is ignored and processing continues.

USER ID IS INVALID (GK619)The specified user ID either is a main administrator number, or contains only blanks,asterisks, and underscores, or is an invalid subadministrator number because it is notalphanumeric.

NAME IS INVALID (GK620)Either the specified name contains only blanks, asterisks, and underscores, or it isinconsistent with the specified user ID (the number is that of a subadministrator butthe name does not begin with a plus sign).

GK615

GK615

GK616

GK617

GK617

GK618

GK619

GK620



OPERATOR MODEL NUMBER WAS NOT ENTERED (GK621)The model number is all blanks. Correct the model number and rerun the job.

OPERATOR MODEL NUMBER IS NOT ON FILE (GK622)The model number must be a valid user ID currently in the security file. Enter avalid model number and rerun the job.

USER ID IS ALREADY ON FILE (GK623)A request was made to add a user ID that is already in the security file. Correct theuser ID and rerun the job.

FIELD MARKED BY 'X' IS TOO LONG (GK624)The specified field contains too many characters. Correct the input and rerun thejob.

MODEL/NAME MARKED BY 'X' IS TOO LONG (GK625)The model or name marked with an X is longer than nine characters. No subsequentmodels or operators are processed. All models or operators prior to the one in errorare processed normally.

INVALID KEYWORD NEAR POSITION XXXXXXXX (GK626)An invalid keyword was detected at the position XXXXXXXX in the control card.Check for proper spelling of the keyword in question.

KEYWORD VALUE TOO LONG NEAR POSITION XXXXXXXX (GK627)A value was specified that is too long for the keyword at position XXXXXXXX in thecontrol record. Check the acceptable values for the keyword indicated.

TOO MANY KEYWORD VALUES NEAR POSITION XXXXXXXX (GK628)At the position XXXXXXXX in the control record, more than the maximum allowablenumber of keyword values are specified. Check the BIM-ALERT/CICS SecurityAdministrator's Guide to determine the maximum number of values.

GK621

GK622

GK623

GK624

GK625

GK626

GK627

GK628



UNPAIRED PARENTHESES NEAR POSITION XXXXXXXX (GK629)The parentheses for the keyword at the position XXXXXXXX in the control record arenot paired properly.

LINECOUNT VALUE MUST BE BETWEEN 10 AND 99 (GK630)A value was specified for LINECOUNT that is either less than the minimum orgreater than the maximum allowed. Correct the value and rerun the job.

UPPER-CASE PARAMETER MUST BE YES OR NO (GK631)The only valid values for UPPER-CASE are YES or NO. Correct the value andrerun the job.

START-DATE AND END-DATE PARAMETERS MUST BE A VALID DATEBETWEEN 01/01/1942 AND 12/31/2041 (GK632)An invalid date was specified for either START-DATE or END-DATE. The datemust be in the format mm/dd/yyyy and in the range specified.

START-TIME AND END-TIME PARAMETERS MUST BE A VALID TIMEBETWEEN 00:00:00 AND 24:00:00 (GK633)An invalid time was specified for either START-TIME or END-TIME. The timemust be in the format hh:mm:ss and in the range specified.

BLOCKSIZE VALUE MUST BE BETWEEN 2800 AND 32767 (GK634)A value was specified for BLOCKSIZE that is not in the accepted range, which isspecified. Correct the value and rerun the job.

INPUT-FILE AND OUTPUT-FILE PARAMETER MUST BE EITHER TAPEOR DISK (GK635)Something other than TAPE or DISK was specified for either the INPUT-FILE orOUTPUT-FILE parameter. Correct the value and rerun the job.

DEVICE SYS-NUMBER MUST BE IN THE RANGE 000 TO 255 (GK636)A value was specified for SYS-NUMBER that is not in the specified range. Correctthe value and rerun the job.

GK629

GK630

GK631

GK632

GK633

GK634

GK635

GK636



ERROR - INPUT CARD DOES NOT CONTAIN EQUAL SIGN (GK637)An equal sign must follow the keyword on the input card. Correct the card and rerunthe job.

ERROR - NO SUFFIX FOUND FOLLOWING EQUAL SIGN (GK638)A suffix must follow the equal sign on the input card. Correct the card and rerun thejob.

ERROR - SUFFIX NOT NUMERIC (GK639)The value of the suffix on the input card must be numeric and in the range of one tonine. Correct the card and rerun the job.

ERROR - SUFFIX CONTROL CARD OMITTED (GK640)A suffix control card is required as input to this program. Refer to the BIM-ALERT/CICS Security Administrator's Guide for correct card format. Code a suffixcontrol card and rerun the job.

PHASE XXXXXXXX NOT DEFINED IN SDL (GK641)An error was encountered during the CDLOAD of the phase S1SCNTRx. Itprobably is not defined in the SDL in your IPL startup.

ERROR CDLOADING PHASE XXXXXXXX (GK642)An error occurred during an attempt to access the BIM-ALERT/CICS controlmodule. Make sure the module has been added to the system entries correctly andrerun the job.

INVALID ADDRESS POINTER IN S1SCNTRL (GK643)An error occurred with BIM-ALERT/CICS's internal address pointers. Contact BIMTechnical Support for assistance.

ERROR VALIDATING VVVVVVVVVVV TABLE R8=XXXXXXXXR9=XXXXXXXX (GK645)An error occurred with one of BIM-ALERT/CICS's internal tables (terminal,operator, transaction, program, file, map, or field-level resource). Contact BIMTechnical Support for assistance.

GK637

GK638

GK639

GK640

GK641

GK642

GK643

GK645



CICS PARTITIONS STILL RUNNING - JOB TERMINATED (GK646)A job was submitted to release BIM-ALERT/CICS tables that are being shared bymultiple CICS regions, but one or more regions are still running. Refer to the BIM-ALERT/CICS Security Administrator's Guide for information about shared BIM-ALERT/CICS tables.

XXXXXXXX KEYWORD OMITTED ... JOB TERMINATED (GK647)The keyword XXXXXXXX is required to run the job, but it was not included in theinput. Add the parameter and rerun the job.

FUNCTION PARAMETER MUST BE EITHER BACKUP OR ARCHIVE(GK648)The value of the FUNCTION parameter must be either BACKUP or ARCHIVE.Correct the value and rerun the job.

THE FOLLOWING UNKNOWN TRANSACTIONS WERE FOUND IN THEBIM-ALERT AUDIT FILE (GK649)One or more records in the BIM-ALERT/CICS audit file contained a transactioncode that was not recognized by the batch audit report program. The transactions arelisted immediately following the error message. Contact BIM Technical Support forassistance.

XXXXXXXX PARTITIONS SHARING TABLES - REPLY NOCICSUP ORCANCEL (GK650)The internal counter maintained in the control module indicates that XXXXXXXXpartitions or regions are still running and using the shared tables. This counter couldbe incorrect if the shutdown PLT program S1S998 was not included in the PLTSD,or if a CICS execution that used the tables abended. To free the tables despite thevalue of the counter, enter NOCICSUP on the operator console. If the message isvalid, enter CANCEL to end job S1U010 without freeing the tables.

VVVVVVVVVVV TABLE POINTER INVALID - REPLY GO OR CANCEL(GK651)One of the internal pointers in the control module contains X'FFFFFFFF' as theaddress of the table. This indicates that the initialization process abended. Enter GOto force the address to be cleared, or CANCEL to cancel the job.

GK646

GK647

GK648

GK649

GK650

GK651



GETMAIN STORAGE EXHAUSTED - JOB TERMINATED (GK675)An attempt to acquire storage failed because not enough storage was available tosatisfy the request. Run the job in a partition that has more GETVIS storageavailable.

STORAGE FAILURE - RETURN CODE = XXXXXXXX (GK676)An attempt to acquire storage failed because not enough storage was available tosatisfy the request. Run the job in a partition that has more GETVIS storageavailable.

GETMAIN STORAGE EXHAUSTED - INCREASE NUMBER ONXXXXXXXX= PARAMETER (GK677)The number coded on the XXXXXXXX=nnnn statement was not large enough for allthe information requested. Specify a larger number and rerun the job.

GK675

GK676

GK677

Informational Messages



The messages in the range GK700 to GK800 are informational and instructionalmessages produced by the various online file maintenance programs.

MOVE CURSOR TO FUNCTION TO PROCESS AND PRESS -ENTER-(GK700)Either move the cursor next to the function you want to process and press ENTER,or press one of the specified PF keys to go to a different menu.

MOVE CURSOR TO FUNCTION TO PROCESS AND PRESS -ENTER-(GK701)Either move the cursor next to the function you want to process and press ENTER,or press one of the specified PF keys to go to a different menu.

ENTER SECURITY SPECIFICATION UPDATES ... PRESS ENTER (GK702)Select the feature you want to turn on or off by placing an X in the appropriate spot.

ENTER PROCESSING PARAMETER UPDATES ... PRESS ENTER(GK703)Enter the updates you want to make to the system parameters in the appropriate inputareas.

ENTER FUNCTION ==> AL=ALL MA=MAX MC=MAX CON DA=DISABLED"M="=ALL MAX (GK704)Enter the selection criteria on the USER panel to select which terminals you want tosee.

ENTER 'X' TO REFRESH A MONITOR/EXIT - LOGONAME TO REFRESHA LOGO (GK705)If you want to refresh a monitor or exit, enter an X by that monitor or exit. If youwant to refresh a logo, enter the name by which the logo is cataloged.

ENTER VVVVVVVVVVV TO BE ADDED TO FILE (GK710)Enter the information for resource type VVVVVVVVVVV that you want to add to theS1SCTY file.

Introduction

GK700

GK701

GK702

GK703

GK704

GK705

GK710



ENTER MAP DISPLAY INFORMATION TO BE ADDED TO FILE (GK710A)Enter the required information to add a secured map.

ENTER VVVVVVVVVVV(S) TO BE UPDATED (GK711)Enter the names of the resources of type VVVVVVVVVVV that you want to update inthe S1SCTY file.

ENTER MAP NAME / REF. # OF MAP SECURITY TO BE UPDATED(GK711A)Enter the map name and reference number to select the map profile you wantupdated in the S1SCTY file.

ENTER VVVVVVVVVVV SECURITY UPDATE INFORMATION (GK711B)Enter the information to be updated for the selected resource of typeVVVVVVVVVVV.

ENTER MESSAGE UPDATES -OR- PF KEYS TO BROWSE (GK711C)Either enter the updates to the message currently displayed, or press the appropriatePF key to continue browsing.

ENTER VVVVVVVVVVV(S) TO BE DISPLAYED, PRESS 'ENTER' (OR)(GK712)This message and message GK713 are issued together.

Either enter the names of the secured resources of type VVVVVVVVVVV that youwant to display, or press PF8 to display all the resources of type VVVVVVVVVVVthat are defined in the S1SCTY file.

PRESS -PF8- TO DISPLAY ALL THE VVVVVVVVVVVS ON FILE (GK713)This message and message GK712 are issued together.

Either enter the names of the secured resources of type VVVVVVVVVVV that youwant to display, or press PF8 to display all the resources of type VVVVVVVVVVVthat are defined in the S1SCTY file.

GK710

GK711

GK711

GK711

GK711

GK712

GK713



ENTER VVVVVVVVVVV TO BE DISPLAYED (OR) PRESS -PF8- TOBROWSE (GK714)Enter the name of the resource of type VVVVVVVVVVV that you want to display,then either press ENTER to display that resource, or press PF8 to start browsing atthat point.

ENTER MAP NAME / REF. # TO BE DISPLAYED (OR) PRESS -PF8- TOBROWSE (GK714A)Enter the map name and reference number of the map you want to display, theneither press ENTER to display the map, or press PF8 to begin browsing throughmaps at that point.

MORE VVVVVVVVVVVS ON FILE ... PRESS -PF8- TO CONTINUE(GK715)Press PF8 to continue browsing the secured resources of type VVVVVVVVVVV.

PRESS -PF8- TO CONTINUE BROWSING (OR) ... (GK716)This message and message GK717 are issued together.

Either press PF8 to continue browsing the secured operators or terminals, or enterthe function code specified in message GK717 to see the operator or terminal'sassociated resources.

(T)=TRANS (P)=PROGS (F)=FILES (M)=MAPS (R)=FLDS (G)=GRPS(N)=NEXT =>( (GK717)This message and message GK716 are issued together.

Either press PF8 to continue browsing the secured operators or terminals, or enterthe function code specified in message GK717 to see the operator or terminal'sassociated resources.

ERASE REQUESTED ... ENTER 'Y' TO VERIFY DELETION OF RECORD == => ( (GK718)You have selected status E, Erase, for an operator or terminal profile. Enter Y toverify this status and delete the record, or enter anything else to cancel the eraserequest.

GK714

GK714

GK715

GK716

GK717

GK718



SUB-ADMINISTRATORS MAY ONLY BE PROCESSED BY MAINADMINISTRATORS (GK719)Only main administrators (those with operator class M) can add subadministrators(those with operator class T or O).

ENTER VVVVVVVVVVV(S) TO BE ADDED TO THE VVVVVVVVVVVV(GK720)Enter the names of the resources of type VVVVVVVVVVV that you want to authorizeto this terminal or operator (VVVVVVVVVVV).

ENTER FILE(S) AND PROCESS INFORMATION TO BE ADDED TO THEVVVVVVVVVVV (GK720A)Enter the file names and the process information to be added to this terminal oroperator (VVVVVVVVVVV).

ENTER THE MAP NAMES / REF. #S TO BE ADDED TO THEVVVVVVVVVVV (GK720B)Enter a map name and reference number to assign the map to the operator or terminal(VVVVVVVVVVV).

ENTER VVVVVVVVVVV(S) TO BE DELETED FROM THE VVVVVVVVVVV(GK721)Enter the names of the resources of type VVVVVVVVVVV that you want to removefrom the profile of this terminal or operator (VVVVVVVVVVV).

ENTER FILES AND PROCESS INFO TO BE UPDATED FOR THISVVVVVVVVVVV (GK721A)Enter the changes in the file status for this terminal or operator (VVVVVVVVVVV).

ENTER THE MAP NAMES / REF. #S TO BE DELETED FROM THISVVVVVVVVVVV (GK721B)Enter the map names and reference numbers of the maps that you want to removefrom the profile of this terminal or operator (VVVVVVVVVVV).

GK719

GK720

GK720

GK720

GK721

GK721

GK721



(B)=BASE (P)=PROGS (F)=FILES (M)=MAPS (R)=FLDS (G)=GRPS(N)=NEXT ==>( (GK722)Enter the specified response to see either the basic profile, the other resourcesassigned to this operator or terminal, or a new operator or terminal.

(B)=BASE (P)=TRANS (F)=FILES (M)=MAPS (R)=FLDS (G)=GRPS(N)=NEXT ==>( (GK722A)Enter the specified response to see either the basic profile, the other resourcesassigned to this operator or terminal, or a new operator or terminal.

(B)=BASE (P)=TRANS (F)=PROGS (M)=MAPS (R)=FLDS (G)=GRPS(N)=NEXT =>( (GK722B)Enter the specified response to see either the basic profile, the other resourcesassigned to this operator or terminal, or a new operator or terminal.

(B)=BASE (P)=TRANS (F)=PROGS (M)=FILES (R)=FLDS (G)=GRPS(N)=NEXT =>( (GK722C)Enter the specified response to see either the basic profile, the other resourcesassigned to this operator or terminal, or a new operator or terminal.

(B)=BASE (T)=TRANS (P)=PROGS (F)=FILES (M)=MAPS (G)=GRPS(N)=NEXT =>( (GK722D)Enter the specified response to see either the basic profile, the other resourcesassigned to this operator or terminal, or a new operator or terminal.

(B)=BASE (T)=TRANS (P)=PROGS (F)=FILES (M)=MAPS (G)=FLDS(N)=NEXT =>( (GK722E)Enter the specified response to see either the basic profile, the other resourcesassigned to this operator or terminal, or a new operator or terminal.

ENTER THE VVVVVVVVVVV NUMBER AND VVVVVVVVVVV(S) TO BEADDED (GK723)Enter an operator or terminal number (VVVVVVVVVVV) and specify which resourcesof type VVVVVVVVVVV you want authorized for that operator or terminal.

GK722

GK722

GK722

GK722

GK722

GK722

GK723



ENTER THE VVVVVVVVVVV NUMBER AND FILE(S)/PROCESS INFO TOBE ADDED (GK723A)Enter an operator or terminal number (VVVVVVVVVVV) and specify which file orfiles and process information you want added to the profile of that operator orterminal.

ENTER THE VVVVVVVVVVV NUMBER AND MAP NAMES / REF. #S TOBE ADDED (GK723B)Enter an operator or terminal number (VVVVVVVVVVV) and specify the names andreference numbers of the maps you want added to the profile of that operator orterminal.

'ALL' VVVVVVVVVVVS AUTHORIZED FOR THIS VVVVVVVVVVV(GK724)This operator or terminal (VVVVVVVVVVV) is authorized to access all resources oftype VVVVVVVVVVV.

NO MAPS RESTRICTED FOR THIS VVVVVVVVVVV (GK724A)This operator or terminal (VVVVVVVVVVV) has no map restrictions.

MORE VVVVVVVVVVVVS ON FILE ... PRESS -PF8- TO CONTINUEDISPLAY (OR) (GK725)This message and either message GK722, GK722A, GK722B, GK722C, GK722D,or GK722E are issued together.

There are more resources of type VVVVVVVVVVV defined in the file. Press PF8 tocontinue browsing, or enter one of the responses listed in the accompanyingmessage.

ENTER VVVVVVVVVVV NUMBER OF VVVVVVVVVVVS TO DISPLAY ...PRESS -ENTER-(GK726)Enter the number of the operator or terminal (VVVVVVVVVVV) whose authorizedresources of type (VVVVVVVVVVV) you want to see.

GK723

GK723

GK724

GK724

GK725

GK726



ENTER THE VVVVVVVVVVV NUMBER AND VVVVVVVVVVV(S) TO BEDELETED (GK727)Enter the number of an operator or terminal (VVVVVVVVVVV) and the names of theresources of type VVVVVVVVVVV you want to remove from the profile of thatoperator or terminal.

ENTER VVVVVVVVVVV NUMBER AND FILE/PROCESS INFORMATIONTO BE UPDATED (GK727A)Enter the number of an operator or terminal (VVVVVVVVVVV) and the changes youwant to make regarding that operator or terminal's authorized files.

ENTER VVVVVVVVVVV NUMBER AND MAP NAME / REF. # TO BEDELETED (GK727B)Enter the number of an operator or terminal (VVVVVVVVVVV) and specify whichmaps you want to remove from that operator or terminal's restricted list.

ENTER VVVVVVVVVVV NUMBER OF VVVVVVVVVVVS TO BEDISPLAYED ... PRESS -ENTER- (GK728)Enter the number of the operator or terminal (VVVVVVVVVVV) whose authorizedresources of type VVVVVVVVVVV you want to see.

ENTER MESSAGE NUMBER TO UPDATE -OR- PF KEY TO BROWSE(GK749)Specify the number of the message in the current message file that you want todisplay or update, or specify the name of another message file and the number of themessage in that file that you want to display or update.

HAVE XXXXXXXX SIGN ON WITH ASSIGNED EXPIRED PASSWORD(GK750)The operator you selected has been assigned the specified password with an expireddate. Have the operator sign on with that password to have BIM-ALERT/CICSeither assign a new password or allow the operator to change the password.

PASSWORDS DO NOT MATCH ... CORRECT/RE-ENTER (GK751)The passwords you entered on the OPWD screen do not match. The passwords mustmatch before BIM-ALERT/CICS will update the operator's record.

GK727

GK727

GK727

GK728

GK749

GK750

GK751



ENTER SCAN ARGUMENT AND STARTING WORD NUMBER (GK752)Enter the data that you want to base the operator or group search on.

UNMATCHED QUOTE DETECTED ... CORRECT/RE-ENTER (GK753)You must enclose in single quotes any search string that includes blanks.

BEGINNING WORD OUT OF RANGE ... MUST BE 1 - 5 (GK754)The number of the starting word must be in the range of 1 - 5.

MORE VVVVVVVVVVVS ON FILE ... PRESS -PF8- TO CONTINUE(GK755)There are more operators or groups (VVVVVVVVVVV) that fit the scan argument.Press PF8 to see the next screen.

NO VVVVVVVVVVVS MATCHING SCAN ARGUMENT (GK756)There are no operators or groups (VVVVVVVVVVV) that match the scan argument.

RESPONSE MUST BE Y OR N ... CORRECT/RE-ENTER (GK757)Enter either Y or N to continue.

UPDATE REQUEST CANCELLED BY USER (GK758)The administrator pressed PF3 and thereby canceled the administrator change orreclaim processing.

ONLY PF7, PF8, OR ENTER ARE SUPPORTED ... CORRECT/REENTER(GK759)Press PF7, PF8, or ENTER to continue.

LOCK FAILURE INTEGRITY ... UPDATES CANCELLED (GK760)Someone else is attempting to update the same set of records. Your update request iscanceled. Try again later.

HIGHLIGHTED FIELDS REQUIRED ... CORRECT/REENTER (GK761)Enter the required fields to continue.

GK752

GK753

GK754

GK755

GK756

GK757

GK758

GK759

GK760

GK761



UPDATE IN PROGRESS FOR CURRENT ADMINISTRATOR - TRY AGAINLATER (GK762)You cannot update the profile of this administrator at this time. Try again later.

NO VVVVVVVVVVVS FOUND FOR CURRENT ADMINISTRATORENTERED (GK763)The specified administrator does not own any terminals or operators(VVVVVVVVVVVs).

ATTEMPTED VIOLATIONS NOW BEING PRINTED (GK769)All violations that satisfy the input criteria have been formatted and sent to thespecified printer for printing.

MORE AUDIT RECORDS ON FILE ... PRESS -PF8- TO CONTINUE(GK770)There are more audit records on file that satisfy the specified input criteria. PressPF8 to continue viewing records.

END OF REQUESTED AUDIT RECORDS (GK771)No more audit records on file satisfy the input criteria.

MORE ATTEMPTED VIOLATIONS ON FILE ... PRESS -PF8- TOCONTINUE (GK772)There are more violation records on file that satisfy the input criteria. Press PF8 tocontinue viewing records.

END OF REQUESTED ATTEMPTED VIOLATIONS (GK773)No more violation records on file satisfy the input criteria.

PRESS -ENTER- FOR VVVVVVVVVVV TIMES PRESS -PF8- FOR NEXTRECORD (GK774)Either press ENTER to see the time changes for the operator or terminal(VVVVVVVVVVV), or press PF8 to see the next audit record.

GK762

GK763

GK769

GK770

GK771

GK772

GK773

GK774



PRESS -ENTER- FOR ADD'L FIELDS ON THIS MAP PRESS -PF8- FORNEXT RECORD (GK774A)There are more field information changes for this map. Either press ENTER to seemore changes or press PF8 to see the next record.

PRESS -ENTER- FOR TASKID ALGORITHM FOR USER PRESS -PF8-FOR NEXT RECORD (GK774B)Either press ENTER to see the task ID algorithm information for this user rule, orpress PF8 to see next record.

PRESS -ENTER- FOR MONITOR PARAMETERS PRESS -PF8- FORNEXT RECORD (GK774C)Either press ENTER to see the monitor information for this SCFL audit record, orpress PF8 to see the next record.

PRESS -ENTER- FOR PROCESSING PARAMETERS PRESS -PF8- FORNEXT RECORD (GK774D)Either press ENTER to see the processing information for this UPAR audit record, orpress PF8 to see the next record.

PRESS -ENTER- FOR TERMINAL PARAMETERS PRESS -PF8- FORNEXT RECORD (GK774E)Either press ENTER to see the terminal information for this UTOP audit record, orpress PF8 to see the next record.

PRESS -ENTER- FOR ADDITIONAL SEGMENTS PRESS -PF8- FORNEXT RECORD (GK774F)Either press ENTER to see additional segments for this field resource, or press PF8to see the next record.

PRESS -ENTER- FOR VVVVVVVVVVV TIMES PRESS -PF8- FORSELECTION PANEL (GK775)Either press ENTER to see the time changes for the operator or terminal(VVVVVVVVVVV), or press PF8 to return to the selection panel.

GK774

GK774

GK774

GK774

GK774

GK774

GK775



PRESS -ENTER- FOR ADD'L FIELDS ON THIS MAP PRESS -PF8- FORSELECTION PANEL (GK775A)There are more field information changes for this map. Either press ENTER to seemore changes or press PF8 to return to the selection panel.

PRESS -ENTER- FOR TASKID ALGORITHM FOR USER PRESS -PF8-FOR SELECTION PANEL (GK775B)Either press ENTER to see the task ID algorithm information for this user rule, orpress PF8 to return to the selection panel.

PRESS -ENTER- FOR MONITOR PARAMETERS PRESS -PF8- FORSELECTION PANEL (GK775C)Either press ENTER to see the monitor information for this SCFL audit record, orpress PF8 to return to the selection panel.

PRESS -ENTER- FOR PROCESSING PARAMETERS PRESS -PF8- FORSELECTION PANEL (GK775D)Either press ENTER to see the processing information for this UPAR audit record, orpress PF8 to return to the selection panel.

PRESS -ENTER- FOR TERMINAL PARAMETERS PRESS -PF8- FORSELECTION PANEL (GK775E)Either press ENTER to see the terminal information for this UTOP audit record, orpress PF8 to return to the selection panel.

PRESS -ENTER- FOR ADDITIONAL SEGMENTS PRESS -PF8- FORSELECTION PANEL (GK775F)Either press ENTER to see additional segments for this field resource, or press PF8to return to the selection panel.

WELCOME ... PLEASE SIGN ON OR TYPE HELP .. TIME IS XXXXXXXXON XXXXXXXX (GK780)This message is displayed at the bottom of the BIM-ALERT/CICS Sign-on screen.

GK775

GK775

GK775

GK775

GK775

GK775

GK780



THE FOLLOWING VVVVVVVVVVV(S) ARE AUTHORIZED VVVVVVVVVVVXXXXXXXX (GK790)This message shows which operators or terminals (VVVVVVVVVVV(s)) areauthorized to access resource XXXXXXXX of type VVVVVVVVVVV.

THE FOLLOWING VVVVVVVVVVV(S) HAVE RESTRICTIONS ON MAP ...XXXXXXXX XXXXXXXX (GK790A)This message shows which operators or terminals (VVVVVVVVVVV(s)) haverestrictions for the map with name and reference number XXXXXXXX XXXXXXXX.

XXXXXXXX VVVVVVVVVVVS AUTHORIZED (GK791)This message reports the total number (XXXXXXXX) of operators or terminals(VVVVVVVVVVVs) authorized to access the specified resource.

GK790

GK790

GK791



CA-ALERT FOR VM REQUEST FAILED - RETURN CODE=rc (GK850)BIM-ALERT/CICS tried to pass a security update to CA-ALERT for VM, but therequest failed. rc indicates one of the following return codes:

Code Meaning






11 The new password matches a previously used CA-ALERT for VMpassword.

13 The new password does not match the CA-ALERT for VM passwordmask.




19 The new password failed the CA-ALERT for VM character repetitioncheck.

CA-ALERT FOR VM REQUEST FAILED - INVALID SUBFUNCTION(GK851)BIM-ALERT/CICS tried to pass a security update to CA-ALERT for VM, but therequest failed. This indicates an internal error in BIM-ALERT/CICS or a storageoverlay. Contact BIM Technical Support for assistance in resolving the problem.

GK850

GK851

Violation Messages


Violation Messages

The messages in this section are those written to the log file and to the operator(when applicable) after a violation has occurred. The messages do not have amessage number associated with them, but they can be located in the message file bythe key shown in parentheses at the end of the message.

In some cases, the last two numbers of the key can be used to display the message onthe DVIO/PVIO screen. Those messages that can be displayed on the DVIO/PVIOscreen are marked by an asterisk (*).

- MAXIMUM SECURITY VIOLATIONS DETECTED - (VIOL04)*

- MAXIMUM CONSECUTIVE VIOLATIONS DETECTED - (VIOL05)*

- SCHEDULED TERMINAL ACCESS TIME EXPIRED - (VIOL06)*

- TERMINAL NOT SIGNED ON - (VIOL08)*

- TERMINAL INACTIVE TIME LIMIT EXPIRED - (VIOL10)*

- OPERATOR NOT SIGNED ON - (VIOL12)*

- OPERATOR PROHIBITED SYSTEM ACCESS - (VIOL14)*

- OPERATOR DISABLED DUE TO MAXIMUM VIOLATIONS - (VIOL15)*

- SCHEDULED OPERATOR ACCESS TIME EXPIRED - (VIOL16)*

- OPERATOR INACTIVE TIME LIMIT EXPIRED - (VIOL18)*

INACTIVE LIMIT EXCEEDED - INVALID PASSWORD (VIOL19)*

TRANSACTION - XXXXXXXX - SCHEDULED ACCESS TIME EXPIRED(VIOL20)*

/*/*/ BIM-ALERT TRANSACTION XXXXXXXX NOW IN PROCESS /*/*/(VIOL22)

TERMINAL UNAUTHORIZED TRANSACTION - XXXXXXXX (VIOL24)*

OPERATOR UNAUTHORIZED TRANSACTION - XXXXXXXX (VIOL26)*

PROGRAM - XXXXXXXX - SCHEDULED ACCESS TIME EXPIRED(VIOL28)*

TERMINAL UNAUTHORIZED PROGRAM - XXXXXXXX (VIOL30)*

(continued)

Introduction

Violation Messages


OPERATOR UNAUTHORIZED PROGRAM - XXXXXXXX (VIOL32)*

FILE - XXXXXXXX - SCHEDULED ACCESS TIME EXPIRED (VIOL34)*

FILE - XXXXXXXX - NOT AUTHORIZED FOR UPDATING (VIOL36)*

TERMINAL DEFINED INQUIRY ONLY - XXXXXXXX (VIOL38)*

TERMINAL NOT AUTHORIZED FILE - XXXXXXXX (VIOL40)*

TERMINAL NOT AUTHORIZED TO UPDATE FILE - XXXXXXXX(VIOL42)*

TERMINAL NOT AUTHORIZED FIELD - XXXXXXXX (VIOL43)*

OPERATOR DEFINED INQUIRY ONLY - XXXXXXXX (VIOL44)*

OPERATOR NOT AUTHORIZED FILE - XXXXXXXX (VIOL46)*

OPERATOR NOT AUTHORIZED TO UPDATE FILE - XXXXXXXX(VIOL48)*

OPERATOR NOT AUTHORIZED FIELD - XXXXXXXX' (VIOL49)*

INCORRECT TERMINAL PASSWORD ENTERED (VIOL50)*

TERMINAL SIGNON COMPLETED (VIOL52)

TERMINAL SIGNOFF COMPLETED (VIOL54)

OUTDATED OPERATOR PASSWORD IN USE (VIOL56)

INCORRECT NAME ENTERED (VIOL58)*

INCORRECT OPERATOR PASSWORD ENTERED (VIOL60)*

OPERATOR ATTEMPTED TO USE AN UNAUTHORIZED TERMINAL(VIOL62)*

INCORRECT USER ID ENTERED (VIOL63)*

OPERATOR SIGNON COMPLETED (VIOL64)

OPERATOR SIGNOFF COMPLETED (VIOL66)

OPERATOR SIGNOFF COMPLETED (VIOL67)

ATTEMPTED TO ACCESS UNASSIGNED RESOURCE (VIOL68)*

TRANSACTION - XXXXXXXX- NOT FOUND IN SECURITY TABLE(VIOL70)*

(continued)

Violation Messages


PROGRAM - XXXXXXXX- NOT FOUND IN SECURITY TABLE (VIOL72)*

FILE - XXXXXXXX- NOT FOUND IN SECURITY TABLE (VIOL74)*

TERMINAL NOT AUTHORIZED INPUT - XXXXXXXX (VIOL76)*

OPERATOR NOT AUTHORIZED INPUT - XXXXXXXX (VIOL77)*

POSSIBLE MAP ALTERATION DETECTED - XXXXXXXX (VIOL78)*

SYSTEM ACCESS ATTEMPTED FROM UNSECURED TERMINAL(VIOL80)*

-> PLEASE CONTACT YOUR SECURITY ADMINISTRATOR <- (VIOL90)

**-> PLEASE PRESS ENTER KEY TO SIGN ON <-** (VIOL92)

**-> ACCESS PROHIBITED <-** (VIOL94)

VIOLATION MESSAGE NOT DEFINED IN MESSAGE TABLE (VIOLFF)

Violation Messages


4-1

4 BIM-ALERT Report Writer Messages

This chapter describes the BIM-ALERT report writer messages and the actions totake in response to them.

About This Chapter....................................................................................................4-2Report Writer Messages ............................................................................................4-3

About This Chapter


About This Chapter

This chapter describes the BIM-ALERT report writing messages. These messagesbegin with ALRT and are issued by program ALRTVREP.

Report Writer Messages

Chapter 4. BIM-ALERT Report Writer Messages 4-3


STMT nnnn INVALID COMMAND: xxxxxxxxStatement nnnn contains a command indicated by xxxxxxxx that is not valid for thisprogram. Review the input parameters and correct the command.

xxxxxxxx MODULE NOT FOUNDThe program or load module indicated by xxxxxxxx is required for execution of thereport, but could not be loaded. Correct the name and resubmit the job.

REPORT DEFINITION INCOMPLETEThe RUN command was encountered before any FIELD or FIELDS commandstatements containing field names were processed. Correct the order of thecommands and resubmit the job.

STMT nnnn INVALID KEYWORD: xxxxxxxxStatement nnnn contains a keyword indicated by xxxxxxxx that is not valid for thecommand being processed. Review the input syntax and correct the keyword.

*FILEID* DATASET HAS INVALID RECORD FORMAT.The dataset allocated to the report output file JCL statement must be defined with afixed length record. Correct the record format and resubmit the job.

AXPSYSIN INPUT INVALID. REASON nnnnAn error was encountered processing the AXPSYSIN input data. This error wascaused by one of the following:

Reason Code Description

0004 The AXPSYSIN JCL statement was not included.

0008 The AXPSYSIN dataset could not be opened for input.

0012 No valid command statements were found.

0016 The dataset was defined with invalid dataset attributes.

0020 An error occurred reading the input dataset.

ALRT001E

ALRT002E

ALRT003E

ALRT004E

ALRT005E

ALRT006E



STMT nnnn INVALID KEYWORD VALUE: xxxxxxxxStatement nnnn contains an invalid keyword value indicated by xxxxxxxx. Reviewthe input syntax and correct the keyword.

STMT nnnn DUPLICATE KEYWORD: xxxxxxxxStatement nnnn contains the keyword xxxxxxxx which has already been specified andprocessed on the current command statement. Review the input syntax and correctthe keyword.

STMT nnnn KEYWORD MISSING: xxxxxxxxThe keyword indicated by xxxxxxxx is required for the command being processed. Ifno keyword is indicated in the message, the command was issued without anykeywords. Review the input syntax and correct the keyword.

INTERNAL ERROR AT OFFSET nnnnAn internal error was found during program execution at offset nnnn. Save theaccompanying diagnostic information and contact BIM Technical Support forassistance.

REPORT EXECUTION ERROR: mmmm-nnnnThe report generation process could not be completed because of an abnormaltermination. Either of the following could have occurred:

• If an error has been encountered during the report definition process, a reasoncode of four is returned. If this is the case, correct the errors and resubmit thereport.

• If an internal error has been encountered, a reason code of USER 0012 isreturned. If this is the case, save the diagnostic information and contact BIMTechnical Support for assistance.

PROCESSING ABORTED DUE TO ERRORThe report generation process could not be completed because of an abnormaltermination. Save the diagnostic information and contact BIM Technical Support forassistance.

ALRT008E

ALRT012E

ALRT016E

ALRT100E

ALRT150E

ALRT151E


Chapter 4. BIM-ALERT Report Writer Messages 4-5

ALRTVREP EXECUTION ABENDThe report generation process could not be completed because of an abnormaltermination. Save the diagnostic information and contact BIM Technical Support forassistance.

LINE LENGTH REQUESTED mmm. LENGTH REQUIRED TO DISPLAYALL FIELDS nnn; OUTPUT FILE RECORD LENGTH ???The report generation process could not be completed because of incompatibleoutput length parameters. The sum of all specified or default field LENGTH valuesmust be less than or equal to the default (133) or the specified LINELEN value.

Also, the default or assumed LINELEN value must be one of the following:

• Less than or equal to the record length determined for the output file to whichthe report is to be written

• 133, if directed to the AXPOUT JCL statement

REPORT COULD NOT BE EXECUTEDThe report could not be produced because an error was encountered, as indicated bythe accompanying error messages. Review the messages and detailed reportdefinition analysis, correct all errors, and resubmit the report.

REPORT FIELD DATA EXCEEDS LINE LENGTHThe report could not be produced because the sum of all specified or default fieldLENGTH values exceeded the default (133) or the specified LINELEN value.Reduce the required line length by shortening the length of a field or the length ofthe report header for a field. As a last resort, remove one or more fields from thereport.

REPORT PROCESSING STATISTICSThis message is issued at abnormal termination. It precedes the record countstatistics for the input file.

FILE ACCESS ERROR (mmmm-nnnn)A file access error occurred The VSAM return code is mmmm and the error code isnnnn. See the IBM publication VSE/VSAM Messages and Codes to determine thereason for this abend.

ALRT152E

ALRT153E

ALRT154E

ALRT155E

ALRT156I

ALRT157E



CONTROL PASSED FROM xxxxxxxxThis message indicates that program xxxxxxxx was in progress at the time oftermination.

STMT nnnn UNBALANCED PARENTHESES IN PREVIOUS STATEMENTThe end of command statement nnnn was reached and at least one unbalanced set ofparentheses was encountered. Review the input syntax and correct the parentheses.

STMT nnnn END OF QUOTED STRING LITERAL NOT FOUNDA quoted string literal was encountered on the command line without a closing singlequote. Quoted string literals cannot be continued to subsequent input lines. Reviewthe input syntax and add the closing single quote.

STMT nnnn INVALID SYNTAX - RUN ABORTEDA syntax error has been detected in the indicated statement. Refer to the BIM-ALERT Auditing and Report Writing Guide for information on the report commandand correct the statement.

NO DIAGNOSTIC ERRORS DETECTEDNo diagnostic errors were detected in the edit phase of the report processing. Thereport phase is ready to be run.

ALRT158I

ALRT201E

ALRT202E

ALRT203E

ALRT204I

5-1

5

Return Codes

This chapter explains the meanings of various types of return codes.

About This Chapter ........................................................................................................5-2Return Code Descriptions ..............................................................................................5-3

File Access Return Codes ..........................................................................................5-3Interval Control Return Codes ...................................................................................5-4Temporary Storage Return Codes..............................................................................5-5Load Request Return Codes.......................................................................................5-6Storage Request Return Codes...................................................................................5-6VSAM Error Codes ...................................................................................................5-7VSE Cancel Codes.....................................................................................................5-9

About This Chapter


About This Chapter

This chapter explains the meanings of the following types of return codes:

• File access• Interval control• Temporary storage• Load request• Storage request• VSAM• VSE cancel

Return Code Descriptions File Access Return Codes

Chapter 5. Return Codes 5-3

Return Code Descriptions

File Access Return Codes

The following table describes the return codes issued in response to file requests:

Code Meaning

X'01' The dataset cannot be located in the FCT. This error indicates that the FCTcontaining the BIM-ALERT files either did not catalog properly or is not the onecurrently in use.

X'02' A logic error. This code indicates either that an internal error occurred, or that theidentified file was not defined properly with IDCAMS (that is, the record length isincorrect), or that the file was not initialized properly using the supplied utilityprogram.

X'04' A segment ID error. This return code should never occur in BIM-ALERT.

X'08' An invalid request. This code indicates that either the FCT parameters for the fileare not properly defined or an internal error occurred in BIM-ALERT.

X'0A' The returned record is from a duplicate dataset.

X'0C' The specified file is not open.

X’OD’ The specified file is disabled.

X'0F' An end-of-file condition has occurred.

X'80' An I/O error. This is probably a hardware problem.

X'81' A record not found condition. This indicates an internal error in BIM-ALERT.

X'82' A duplicate record condition. This indicates an internal error in BIM-ALERT.

X'83' The file is full. Either delete and redefine the file, or back up the file and restore itwith a larger allocation.

X'84' A duplicate key condition. This probably indicates an internal error in BIM-ALERT.

X'D0' The file being accessed is owned by a region that is not currently active.

X'D1' An invalid intersystem communications request has been issued to a remotesystem.

X'D6' The user is not authorized the file. To prevent this return code from CICS, defineyour files as PUBLIC. All BIM-ALERT/CICS files should be defined asPUBLIC.

X'E1' This probably indicates an internal error in BIM-ALERT/CICS if it occurs againsta BIM-ALERT file.

Interval Control Return Codes Return Code Descriptions


Interval Control Return Codes

The following table describes the return codes issued in response to interval controlrequests:

Code Meaning

X'01' The requested data could not be located. This suggests that the interval controldata has been purged from temporary storage.

X'04' A permanent I/O error in the auxiliary temporary storage dataset. This is probablya hardware error.

X'11' The transaction ID to be started is not defined in the PCT. This suggests either thatthe program attempting to do the interval control request has been corrupted or thatyou forgot to define the transaction ID in the PCT.

X'12' The terminal to which the task is to be started either is not in the TCTTE or is notcurrently allocated.

X'14' Temporary storage services are not supported in the system.

X'20' The ICE has already expired.

X'81' The requested data cannot be found, either because some other task has alreadyretrieved it, or because it was created with a non-unique name. This suggests aninternal error in BIM-ALERT.

X'D0' A SYSID error.

X'D1' An invalid request across an ISC link.

X'E1' A length error. This suggests an internal error in BIM-ALERT.

X'E9' The retrieve command was issued with an option not specified on the STARTcommand. This suggests an internal error in BIM-ALERT.

X'FF' The interval control command that was issued is not supported by your CICSsystem.

Return Code Descriptions Temporary Storage Return Codes


Temporary Storage Return Codes

The following table describes the return codes issued in response to temporarystorage requests:

Code Meaning

X'01' The item number specified in the request is invalid. This suggests an internal errorin BIM-ALERT.

X'02' The temporary storage queue that was requested does not exist. Either it has beenpurged via CICS services, the BIM-ALERT program issuing the request has beencorrupted, or an internal error has occurred in BIM-ALERT.

X'04' A permanent I/O error in the auxiliary temporary storage dataset. This is probablya hardware error.

X'08' No space remains in the temporary storage dataset.

X'20' An invalid request. This suggests an internal error in BIM-ALERT.

X'D0' A SYSID error.

X'D1' An invalid request across an ISC link.

X'E1' A length error. This suggests an internal error in BIM-ALERT.

Load Request Return Codes Return Code Descriptions


Load Request Return Codes

The following table describes the return codes issued in response to a request to loada module into virtual storage via operating system services:

Code Meaning

000 Load completed successfully.

004 The amount of virtual storage allocated is sufficient.

008 The amount of storage requested was a negative number. This suggests an errorduring linkage editing.

012 There is not a large enough chunk of contiguous virtual storage remaining in whichto load the module.

016 The load directory is full.

020 The module to be loaded does not exist in any library in the search chain. Ensurethat the search chain is specified correctly.

032 A hardware error occurred.

Storage Request Return Codes

The following table describes the return codes issued in response to a request forvirtual storage via operating system services:

Code Meaning

000 Storage was acquired successfully.

004 The amount of virtual storage allocated is 0K.

008 The amount of storage requested was a negative number. This suggests an internalerror in BIM-ALERT.

012 There is not a large enough chunk of contiguous virtual storage remaining tosatisfy the request.

032 A hardware error occurred.

Return Code Descriptions VSAM Error Codes


VSAM Error Codes

The following table describes some of the most common VSAM error codes. In allVSAM errors, both a return code (R15) and an error code are available to helpcorrect the problem. In all error codes described in this section, the return code inR15 is X'08'.

If the error code you received is not listed here, refer to the IBM publicationVSE/VSAM Messages and Codes.

Code Meaning

X'04' The ACB has already been opened. This suggests an internal error in the programthat caused the error.

X'08' A duplicate key has been detected during an add operation. This suggests aninternal error in the program that caused the error.

X'0C' The record being added is out of sequence. This can happen only duringinitialization, and it suggests an internal error in the initialization program thatcaused the error.

X'0E' The unit specified on the EXTENT card does not match any of the extents for thecatalog. This is most likely a JCL error. Remove the EXTENT card and try again.

X'10' The requested record was not found on the file. This suggests either some problemon the file or an internal error in the program causing the error.

X'14' The CI containing the record requested is already exclusively held by anotherrequest. This suggests a logic error in the program causing the error.

X'1C' There are no more available extents (the file is full). Either the file was definedwith no secondary allocation, all the available secondary extents have been used, orthere is no more space available in the catalog to allocate secondary extents.

X'22' The VOLSERS specified on the ASSGN or EXTENT do not match those specifiedin the catalog. This suggests a JCL error. Correct the JCL statements in error (orremove them) and try again.

X'32' Insufficient GETVIS is available for VSAM processing. Either rerun the job in alarger partition, or decrease the SIZE on the EXEC card.

X'48' The file ID specified on the DLBL card cannot be found in the catalog. Mostlikely, either the file ID is misspelled or you are accessing the wrong catalog.Check the spelling of the file ID and insert a DLBL for IJSYSUC with the correctcatalog specified, and then try again.

X'4F' A catalog management error was detected during an implicit define of a file. Mostlikely, there is not enough class 0 space available in the catalog to perform theimplicit define. Try doing the implicit define in a different user catalog.

(continued)

VSAM Error Codes Return Code Descriptions


Code Meaning

X'6E' You have either attempted to open an empty file as input or tried to do a keyedinsert into an empty file. The most likely cause of this is that you have defined thefile but not executed the proper initialization program to load it. Try doing theimplicit define in a different user catalog.

X'80' There is no DLBL in the job for the file being opened. This suggests a JCL error.Either the DLBL has been omitted altogether, or the filename has been misspelled.Correct the error and try again.

X'88' Insufficient GETVIS is available for VSAM processing. Either rerun the job in alarger partition, or decrease the SIZE on the EXEC card.

X'94' There is no entry in the accessed catalog for the file being opened. Most likely,either the file ID is misspelled, or you are accessing the wrong catalog. Check thespelling of the file ID and insert a DLBL for IJSYSUC with the correct catalogspecified, and then try again.

X'A8' The file being opened is not available to be opened for output because it is alreadyopened for exclusive control by some other task. Wait until the file is availableand try again. It is likely that CICS is the task that has the file open.

X'FF' Either there is insufficient GETVIS in the partition for VSAM processing, or thereare not enough programmer logical units specified for the partition. Try eitherrunning the job in a larger partition or making the SIZE on the EXEC card smaller.

Return Code Descriptions VSE Cancel Codes


VSE Cancel Codes

The following table describes some of the most common VSE cancel codes. If thecode you received is not listed here, refer to the IBM publication VSE Messages andCodes.

Code Meaning08 Subsystem cancel request.

09 LIOCS cancel request.

10 Normal end of job.

11 No EXCP translation for unsupported device.

12 Insufficient buffer space for channel program translation.

14 Page pool too small.

15 Page fault in disabled program.

16 Error in privately translated CCW.

17 Program request that causes dump. Subtasks attached when main task cancels.

18 Eliminates cancel message when task issues DUMP macro with subtasksattached.

19 I/O operator option.

20 Program check.

21 Illegal SVX.

22 Phase not found.

23 Program request.

24 Operator intervention (cancel).

25 Invalid address.

26 SYSxxx not assigned.

27 Undefined LU.

28 Phase too large for LTA or partition.

29 Invalid sublibrary structure.

30 Reading past end on SYSRDR or IPT.

32 Invalid DASD address.

33 Invalid first CCW.

34 GETVIS space exhausted.

35 Job control open failure.

36 Program check/page fault in I/O appendage.

38 Wrong privately translated CCW.(continued)

VSE Cancel Codes Return Code Descriptions


Code Meaning39 Invalid CCW chain for SYSLOG.

40 ACF or VTAM error (termination of task).

41 ACF or VTAM error (invalid condition code).

42 Violated DASD file protect.

44 Security manager error.

45 Amode or Rmode violation.

46 Data space services.

0A Procedure error in access control.

0B Access control violation.

0C Execution failure in ICCF interactive partition.

0D Program check in subsystem or appendage.

0E Page fault in subsystem or appendage.

0F Invalid access to system file on FBA.

1A I/O error.

1B Channel failure.

1C CANCEL ALL macro issued.

1D Main task termination.

1E I/O error on lock file.

1F CPU failure.

2A I/O error on page dates.

2B I/O error during library fetch.

2C Illegal parameter passed by PHO routine.

2D Failing storage block.

2E Invalid resource request, possible deadlock.

2F More than 255 PFIX requests for one page.

3A Spool request out of sequence.

3B Cancel request by OCCF.

3C Cancel request by OCCF.

3D Error during fetch PFIX.

6-1

6

Abend Codes

This chapter describes the abend codes that might be displayed when you try toinitialize BIM-ALERT/CICS.

About This Chapter ........................................................................................................6-2Abend Codes ..................................................................................................................6-3

About This Chapter


About This Chapter

This chapter describes the abend codes that might be displayed when you try toinitialize BIM-ALERT/CICS. These codes indicate serious problems that must beresolved for BIM-ALERT/CICS to work correctly. In most cases, one of the GKnnnmessages described in Chapter 3, "BIM-ALERT/CICS Messages", will be displayedon the system console in addition to the abend code.

These codes may be displayed at the terminal, and they also appear in the CICStransaction dump produced. The table on the following page is provided to help youassociate the CICS dumps with console messages.

If you cannot resolve a problem, contact BIM Technical Support for assistance. Forinformation about contacting Technical Support, refer to the Preface.

Abend Codes

Chapter 6. Abend Codes 6-3

Abend Codes

AbendCode

RelatedMessage Explanation

FExx None File error. xx represents the EIBRCODE identifying the error condition. For a complete list ofEIBRCODEs and their meanings, see page 5-3.

S001 GK043 See the description of message GK043 on page 3-7 for an explanation.


S003 GK075 The S1SCTY file is not open. Also check the console for VSAM messages.


S005 None Could not release the S1SCTY file work area.


S009 None File error on the S1SCTY file.

S010 GK075 S1SCTY file is not open.

S011 GK076 Transaction control record not found.

S012 GK075 S1SCTY file error.


S014 GK076 Program control record not found.



S017 GK076 File control record not found.



S020 GK076 Map control record was not found.

S022 GK075 File work area storage could not be released for the S1SCTY file.

S141 None EXEC CICS START TRANSID(S145) failed in S1S140.

S142 None EXEC CICS START TRANSID(S145) failed in S1S140.

S146 None EXEC CICS RETRIEVE failed in S1S144 or S1S145.

S147 None EXEC CICS LINK PROGRAM(S1S147) failed in S1S145.


S610 None Program linking to SIS610 does not have the required TWA size.

S615 None GETMAIN for TIOA failed in program S1S615.

Abend Codes


Date post:	07-Aug-2021
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

Release 5 · 2020. 10. 13. · Conventions Overview 1-4 BIM-ALERT Messages Guide A file containing...

Documents