Relational Arc - ftpdocs.broadcom.com

RLX REXX Language Xtensions

Messages and

Codes

Version 9.1.6

November 2016

Publication RLX-101-6

Relational Architects Intl

____________________________________________________________ This Guide: (RAI Publication RLX-101-6) This document applies to RLX Version 9 Release 1 Mod 6 (November 2016), and all subsequent releases, unless otherwise indicated in new editions or technical newsletters. Specifications contained herein are subject to change and will be reported in subsequent revisions or editions. Purchase Orders for publications should be addressed to:

Documentation Coordinator Relational Architects Intl. Riverview Historic Plaza 33 Newark Street Hoboken NJ 07030 USA Tel: 201 420-0400 Fax: 201 420-4080

Reader comments regarding the product, its documentation, and suggested improvements are welcome. A reader comment form for this purpose is provided at the back of this publication. Copyright (c) 1992, 2016 by Relational Architects, Inc. (RAI) as an unpublished work -- all rights reserved. The software product(s) described herein and the documentation thereof are trade secrets and property of Relational Architects, International Inc. All use, disclosure, duplication, electronic storage, reproduction or transmission without specific written authorization from RAI is strictly prohibited. These products may also be protected under the trade-secret and copyright laws of countries other than the United States and international agreements. DB2, SQL/DS, SPUFI, QMF and ISPF are software products of IBM Corporation. RLX, REXX Language Xtensions, AcceleREXX, RLX/SQL, RLX/TSO, RLX/REXX, RLX/CLIST, RLX/ISPF, RLX/VSAM, RLX/SDK, RLX/Edit, RLX/Net, RLX/MVS, RLX/Compile, RLX/CAF, RLX/IFI, RLX/Translate, Multi/CAF, RFA and LMD are trademarks of Relational Architects International, Inc.

Ed 16C02 ____________________________________________________________

Table of Contents 1

Table of Contents

RLX Product Messages ..................................................................................... 1-1

Messages issued by RLXM, RLXS, RLXE, RLXT Modules .................................................. 1-1

RLX Table Display Service Messages ....................................................................................... 1-10

DB2 Command Executive ........................................................................................................... 1-12

Messages issued by RLX Product Dialogs .................................................................................. 1-12

Messages associated with generic SQL routines ......................................................................... 1-16

RLX/Compile Messages.................................................................................... 2-1

RLX/Compile Run-time messages ............................................................................................... 2-1

RLX/Compile Dialog Messages ................................................................................................... 2-1

RLX/Compile Adminstrative Messages ........................................................................................ 2-2

RLX/CAF Messages and Codes ....................................................................... 3-1

1.1 Abend Codes ...................................................................................................................... 3-1

1.2 Messages ............................................................................................................................ 3-2

1.2.1 General RLX/CAF messages ................................................................................ 3-2

1.2.2 CONNECT, DISCONNECT, OPEN and CLOSE messages ............................ 3-6

1.2.3 Error messages related to application thread .......................................................... 3-9

1.2.4 Informational messages related to application threads ......................................... 3-12

1.2.5 Command parser messages .................................................................................. 3-14

1.2.6 Run-time parameters parser messages ................................................................. 3-17

1.2.7 General purpose application thread messages ...................................................... 3-19

RLX/SDK Messages ........................................................................................... 4-1

2 RLX Messages and Codes

RLX/VSAM Messages ...................................................................................... 5-1

REXX/BDAM Messages ................................................................................... 6-1

Reusable Function Architecture (RFA) Messages ......................................... 7-1 Data Conversion Messages ......................................................................................................... 7-1

MVS Messages .......................................................................................................................... 7-2

Messages associated with generic OS/MVS routines ............................................................... 7-3

Numeric Input Conversion Messages ......................................................................................... 7-3

Date conversion routine messages .............................................................................................. 7-4

Time conversion routine messages ............................................................................................. 7-4

Time and timestamp conversion routine messages ..................................................................... 7-5

Miscellaneous Messages for PSR common routines ................................................................ 7-5

Reusable Function Architecture Messages ................................................................................. 7-5

AcceleREXX Messages ..................................................................................... 8-1

AcceleREXX Compile Messages .................................................................................................. 8-1

AcceleREXX Dialog Messages ..................................................................................................... 8-1

Relational Architects Common Messages ........................................................ 9-1

RAI Product Password Verification Messages .............................................................................. 9-1

RAI Product Administration Messages ........................................................................................ 9-4

Member List Dialog (MLD) Messages ......................................................................................... 9-5

User SVC dialog Messages ........................................................................................................... 9-6

Abend Detection Messages ........................................................................................................... 9-7

RLX Product Messages 1-1

RLX Product Messages

This section lists messages issued by RLX product components during RLX installation dialogs, RLX invocation and during RLX execution. Messages are classified by the invoking function.

Messages issued by RLXM, RLXS, RLXE, RLXT Modules

RLX001 Requested EXEC &RLXEXEC was not found in the SYSPROC

concatenation RLX002 RLX experienced a severe error in invoking exec &EXEC RLX003 The RLX Control Table could not be loaded - Execution impossible. RLX004 DB2 Subsystem &RLXDSN was quiesced by the operator RLX005 DB2 Subsystem &RLXDSN was forcibly terminated by the operator RLX006 DB2 Subsystem &RLXDSN experienced an abnormal termination RLX007 DB2 Subsystem &RLXDSN is no longer active RLX008 Supply RLX session parameters and press ENTER RLX009 No target EXEC identified in SELECT CMD string RLX010 Unrecognized RLX process id supplied as RLXTCECB post code'. RLX011 ENTER RLX interruption option or END / RETURN to resume

processing'. RLX014 RLX exhausted connection retry attempts to DB2 subsystem

&RLXDSN RLX015 RLXS RETRY keyword expects retry count within parentheses

1-2 RLX Messages and Codes

RLX016 RLXS RETRY keyword requires a zoned decimal retry count value RLX017 Compiled Exec Block for Exec &XCTEXEC not found RLX018 RLXS SYSTEM keyword expects subsystem name within parentheses RLX019 RLXS must be SELECTed as a CMD rather than as a PGM RLX020 Exec name up to 8 characters with the first character alphabetic RLX021 Specify the name of a DB2 subsystem with which you wish to connect RLX022 Specify a DB2 connection retry count from 0 to 120 RLX023 Specify 2 decimal digits - max standalone SELECT and DECLARE

CURSOR RLX023A Specify 3 alphabetic characters as a name prefix RLX024 Specify C - Cursor Stability or R - Repeatable Read RLX025 Specify Y - activate RLX tracing or N - RLX tracing not active RLX026 Specify I - Integer, E - Edited Decimal as a default numeric format RLX027 Specify 2 decimal digits - Max DELETE, INSERT, UPDATE

statements RLX028 Specify maximum CPU utilization in seconds before work is suspended RLX029 Specify time limit after which resources are released automatically RLX030 RLX variable initialization processing failure RLX031 Specify RLX defaults and press ENTER or press END / RETURN to

exit RLX032 Defaults for an RLX copy / DB2 subystem being tailored - please wait RLX033 Press Enter to tailor Assemble/Link Edit job or END/RETURN to

bypass RLX034 The RLXS commands RLXPROF keyword requires a Profile name RLX035 The RLX Session Profile module &RLXPROF could not be loaded RLX036 RLX defaults assembly/linkedit job being tailored - please wait RLX037 Specify second set of RLX defaults and press ENTER RLX038 RLX internal error - Unable to acquire Logical Screen Block RLX039 Specify third set of RLX defaults and press ENTER


RLX040 RLX deliberately terminating due to unrecoverable error RLX041 File Tailoring in progress - Please wait RLX042 RLX deliberately abending in response to ATTENTION CANCEL

request RLX043 Specify RLX EXEC name - NOT a dataset name (member name) RLX044 The RLX command procedure name may not exceed 8 characters in

length RLX045 Specify a command procedure name may - NOT a qualified dataset

name RLX046 The implicit EXEC command %CMDNAME is greater than 9

characters long RLX047 RLX deliberately terminating due to an error in its own processing RLX048 RLX deliberately terminating due to an abend within DB2 RLX050 Exec name up to 8 characters with the first character alphabetic RLX051 Specify the name of a DB2 subsystem with which you wish to connect RLX052 Specify a DB2 connection retry count from 0 to 120 RLX053 Specify maximum CPU utilization in seconds before work is suspended RLX054 Specify time limit after which resources are released automatically RLX055 Specify 3 alphabetic characters as a prefix for plan/loadmod names RLX056 Specify 2 decimal digits - max standalone SELECT and DECLARE

CURSOR RLX057 Specify 2 decimal digits - Max DELETE, INSERT, UPDATE

statements RLX058 Specify isolation level of (C)ursor Stability or (R)epeatable Read RLX059 Y or N - Merge RLX defaults with individual ISPF profile values RLX060 Select (C)ancel, (F)ilter, or (R)eturn as an error response RLX061 Should an RLX panel describing the error be (D)isplayed or (N)ot? RLX062 Should a CURSOR name be recognized (L)ocally or (G)lobally? RLX063 Should the default numeric format be (I)nteger or (E)dited decimal? RLX064 Most significant digits in range of 1 - 15


RLX065 Specify integer value between 0 and 255 as a Tracing Option RLX066 Select (C)ancel or (R)eturn for an ISPF CONTROL ERRORS setting RLX067 Review and revise your RLX Session Profile attributes RLX068 Your RLX Session Profile was updated successfully RLX069 Specify integer value from 0 thru 999,999 for maximum rows retrieved RLX070 Dynamic SQL source module is being tailored - Please wait RLX071 Press ENTER to tailor and submit BIND/LINK jobstream or END to

exit RLX072 Program preparation jobstream being tailored - Please wait RLX073 Error allocating RLX File Tailoring Library RLX074 Specify dynamic SQL module characteristics and press ENTER RLX075 Press ENTER to tailor jobstream. You can then EDIT and SUBMIT it RLX076 Valid underscore replacement character is A-Z, #, $, or @ RLX077 Verify DB2 libraries for proper Version and Release and press ENTER RLX078 Specify E to Extend previous ISPF table or D to Delete prior result RLX079 Specify integer value from 0 thru 99 for maximum ATTENTION

requests RLX080 Specify up to 8 alphameric characters with the first alphabetic RLX081 Specify a name of up to 8 alphameric characters with first alphabetic RLX082 Specify integer value from 1000 through 99999 for maximum tokens RLX090 Specify (I)SO, (U)SA, (E)UR, or (J)IS format - No LOCAL support yet RLX091 Should a host variable name be recognized (L)ocally or (G)lobally? RLX092 Specify a Host variable Declare option in range 1 to 3 RLX093 Should statement strings be recognized (L)ocally or (G)lobally RLX094 Select code for White, Red, Blue, Green, Pink, Yellow, or Turquoise RLX095 Set RLX return code to S - SQLCODE, N - nonzero or Z - zero RLX096 Specify a valid high level qualifier for a dataset name RLX097 Specify a valid year - 91


RLX100 Select Host variable datatype definition method of 1, 2, or 3 RLX101 Should RLX search for explicit host VDEFINES (1) or not (2) RLX102 Select a host datatype review option of 1, 2, or 3 RLX103 Do you wish to review and revise your RLX profile? - Y or N RLX200 Specify RLX Installation Parameters and press ENTER RLX201 RLX Installation Parameters updated successfully RLX202 Verify RLX library dataset names and press ENTER RLX203 Specify IBM system load libraries and press ENTER RLX204 Specify RLX Job and Jobparm values and press ENTER RLX205 Specify RLX DB2 object CREATE parameters and press ENTER RLX207 RLX Demonstration table &RLXTABLE created successfully RLX208 Create of RLX Demo table &RLXTABLE failed. SQLCODE =

&SQLCODE RLX209 Unable to set current sqlid for &RLXSCOWN,

SQLCODE=&SQLCODE RLX210 Verify RLX Target Dataset Names and press ENTER RLX211 Verify IBM datasets referenced by RLX jobstreams and press ENTER RLX212 Specify DB2 load utility parameters and press ENTER RLX213 Verify names of RLX datasets to be loaded into RLXADM table RLX214 Verify names of IBM datasets to be loaded into RLXADM table RLX215 Specify a Utility Identifier of up to 16 characters RLX216 Specify 1 - Edit tailored jobstream or 2 - Immediately submit job RLX217 PLAN_TABLE for the SQL EXPLAIN function created successfully'

job RLX218 Attempt to create PLAN_TABLE failed with a SQLCODE of

&SQLCODE RLX219 Specify Y for yes or N for No RLX220 RLX attach error - RLXS must terminate RLX221 Error attaching RLXE EXEC driver process - RLXS must terminate


RLX222 Error attaching RLXE EXEC driver process - RLXS must terminate RLX223 Specify S - Static, D - Dynamic, or B - Bypass RLX224 RLX load module could not be located - RLX must terminate RLX230 Select modules for Link Edit or enter END command to exit RLX231 Link Edit jobstream being tailored - please wait RLX232 Specify libraries and job parameters before tailoring defaults RLX233 Tailor RLX Installation Defaults before tailoring plan(s) RLX234 Specify (B)efore or (A)t DB2 Version 1 Release 3 (or later) RLX240 RLX variable initialization processing failure RLX241 ENTER RLX shared profile values or press END / RETURN to exit RLX242 RLX Shared Profile table being tailored - please wait RLX243 Press Enter to tailor Assemble/Link Edit job or END/RETURN to

bypass RLX244 The RLXS commands RLXPROF keyword requires a Profile name RLX245 The RLX Session Profile module &RLXPROF could not be loaded RLX246 RLX Shared Profile assembly/linkedit job being tailored-please wait RLX247 Specify second set of RLX Shared Profile definitions and press ENTER RLX248 Specify third set of RLX Shared Profile definitions and press ENTER RLX250 Cannot identify command procedure name - execution impossible RLX251 Failed to create RLX REXX language processor environment RLX252 Failed to locate RLX ENVBLOCK - execution impossible RLX253 Failed to preload RLXH (RLX Host Command Environment) RLX254 Failed to remove RLX REXX language processor environment RLX300 Invalid scroll amount - request not honored RLX310 The PUT statement (for block insert) is not supported by DB2 RLX311 The RxSQL XCALL statement is not supported in the DB2

environment


RLX312 The RxSQL XPREP statement is not supported in the DB2 environment

RLX313 DROPSTMT (for extended dynamic SQL) not supported in DB2

environment RLX320 Non 00 value for CURSORs WITH HOLD requires DB2 V2.3 or later

release RLX321 Specify 2 decimal digits - max number of DECLARE CURSOR WITH

HOLD RLX322 There is no thread for a DB2 plan established yet RLX323 The prepared statement name was not found RLX324 Prepared statement not purged - internal error RLX325 Internal error - dynamic plan bitmap was not acquired/initialized RLX326 RXSNAMES failed to acquire RXSQLNAMES buffer RLX327 RXSNAMES failed to externalize the value of RXSQLNAMES RLX328 RLX does not let you change the isolation level of an active plan RLX329 RXSSTMT failed to externalize the value of RXSQLSTMT RLX330 Referenced statement is already purged RLX331 Statement cannot be purged because it is not assigned a name RLX332 Statement cannot be purged because it is not assigned a name RLX333 No statement name followed PURGE verb RLX334 An active prepared statement by this name already exits RLX335 The USING option of the OPEN statement is not supported RLX336 The USING option of the CALL statement is not supported RLX337 The TABLE or view option of DESCRIBE is not currently supported RLX338 RXSSTATE failed to externalize the value of RXSQLSTATE RLX340 Host Command &RLXHCN not found as a load module RLX341 Compiled SQL load module &rlxpgm does not contain DBRM

&xcbexec RLX342 No statement &xcbcs# in load module &rlxpgm / CSECT &xcbexec RLX343 Bind of precompiled EXR failed with return code &PDFRC


RLX344 Reference to Declared CURSOR could not be resolved RLX345 Precompiled EXEC invoked without static or hybrid program and/or

plan RLX346 Do not invoke host command &RLXHCN through ADDRESS RLX RLX350 Plan and load module &RLXCPLAN referenced by statement is not

active RLX351 Plan &RLXPLAN makes no provision for dynamic SQL - Respecify

planname RLX352 Failed to load RLX/Compile module RCSG - compilation impossible RLX353 Requested CONTROL XBFC service when not in Compile Mode RLX354 RLX/Compile requires a plan with Dynamic SQL capability RLX355 Specify the name of a DB2 application plan RLX356 Specify the name of a static SQL load module RLX360 Dynamic SQL not supported by static DB2 plan &PSQAPN RLX361 RLXS RLXPGM keyword expects program name within parentheses RLX362 RLXS RLXPLAN keyword expects DB2 plan name within parentheses RLX363 The password module for RLX/Compile (module RCS$TPV) was not

found RLX364 The passwords for RLX/Compile are not valid RLX365 RLXS RLXAUTH keyword expects an authid to qualify DB2 tables RLX366 RLXS RLXMODE keyword expects a mode value within parentheses RLX367 Token is not a recognized RLXMODE value RLX368 Token does not describe a legitimate RLX operational mode RLX369 There is no existing DB2 connection or plan to support

SHARE_THREAD RLX370 Specify BIND attributes for shared thread IVP &rshplan RLX371 Plan BIND jobstream for IVP &rshplan processed sucessfully RLX372 Please wait while DB2 BIND control statements are tailored RLX373 Please wait while DB2 BIND jobstream is tailored


RLX374 Specify RLX SQL load modules for RLXHLI replacement RLX375 The DECLARE REXXSTEM service is not supported by the RLXS

frontend RLX400 Public access to the RLX sample tables was granted successfully RLX401 Specify a DB2 release of 1.3, 2.1, 2.2, 2.3 or 3.1 RLX402 Specify DB2 related parameters for &raicprod installation RLX403 Please wait while the &raicprod install jobstream is being tailored RLX404 Review and submit the AcceleREXX compile and run IVP jobstream RLX405 Revise high level qualifiers of RLX system libraries and press ENTER RLX406 High level qualifiers of RLX system libraries updated successfully RLX407 Execute authority on RLX DB2 plans granted successfully RLX408 Grant of execute authority on RLX DB2 plans was not successful RLX409 Grant of all privileges on RLX sample tables was not successful RLX410 The REXX parameter module IRXISPRM could not be loaded RLX411 The RLX host command environment is not defined RLX412 The REXX local function package supplied with RLX is not defined RLX413 A valid REXX environment for RLX operation does not exist RLX420 The activation status of one or more RLX components has changed RLX421 A status of "Y" enables a component for use while "N" deactivates it RLX422 Change activation status of RLX components as appropriate RLX423 Press ENTER to review RLX component status or PF3 to exit RLX424 Activation status of RLX components being determined - please wait RLX425 No changes to the activation status of any RLX components RLX426 Specify parameters for the RLX dynamic SQL plans and press ENTER RLX427 RLX user profile successfully refreshed with RLX system defaults RLX940 Select (A)dd, (C)hange, (D)elete or (B)rowse or press END to exit RLX941 Browse RLX profile or press END to exit RLX942 Valid selections are (A)dd, (C)hange, (D)elete or (B)rowse


RLX943 Press ENTER to delete profile &RPSNAME or END to bypass delete RLX944 Delete of profile &RPSNAME was successful RLX945 Delete of profile &RPSNAME was NOT successful RLX950 Specify a DB2 Version/Release like 8.1, 9.1, 10.1 RLX Table Display Service Messages RTD001 RLX internal error - Failed to acquire an RTD control block RTD002 Cursor name referenced by the SQLCSR operand was never

DECLAREd RTD003 No FETCH statement references the cursor name RTD004 Specify either CAPS(ON) or CAPS(OFF) RTD005 Specify either INDICATOR(YES) or INDICATOR(NO) RTD006 Specify either SELECT(YES), SELECT(NO), SELECT(ON), or

SELECT(OFF) RTD007 Specify either TYPE(INPUT) or TYPE(OUTPUT) RTD008 RLX TBDISPL operands must follow the ISPF PANEL(name) operand RTD009 RLX TBDISPL statement with PANEL operand must precede this

statement RTD010 Specify either RMO(YES) or RMO(NO) RTD011 RLX TBDISPL statement too long - overflow occurred RTD012 ISPF table name referenced by RLX TBDISPL was never DECLAREd RTD013 Internal RLX TBDISPL session initialization error RTD014 Failed to acquire source heading block required by RLX TBDISPL RTD015 Failed to acquire target block required by RLX TBDISPL RTD016 Failed to acquire ZNAME place holder block required by RLX

TBDISPL RTD017 Failed to acquire ETV control block required by RLX TBDISPL


RTD018 Extraneous or invalid scroll request parameter(s) RTD019 Command requires parameter(s) RTD020 Command is not recognized by the RLX table display service RTD021 ISPF table referenced by RLX TBDISPL statement is not open RTD022 Severe error occurred on TBQUERY against ISPF table RTD023 Non zero return code from RTDIPR - TBDISPL processing failed RTD024 Column name referenced in namelist not associated with table

&RTDITN RTD025 Column reference must be variable name or ordinal column number RTD027 Initialized Message ID for the RLX TBDISPL service RTD028 RLX Tbl Services load failed &PMVAC/&PMVARC - May not be

installed RTD029 The RLX TBDISPL service only accepts a panel name of RLX at this

time RTD030 Cannot make indicator variable mappable when main variable is

frozen RTD031 Sum of lengths of frozen variables limited to logical screen width RTD032 SQL query result and ISPF table variables do not correspond RTD033 Variable length > Panel width: Temporarily not supported RTD034 Unable to scroll right from current position RTD035 Unable to scroll left from current position RTD036 RLX TBDISPL operand must follow the PANEL(panel_name) operand RTD037 RLX TBDISPL SELECT command accepts only YES/NO or ON/OFF RTD038 Error in RLX TBDISPL operand namelist at or before flagged token RTD040 RLX TBDISPL ZCMD operand accepts only YES/NO or ON/OFF RTD041 TSO command limiting in effect - No command entry permitted


DB2 Command Executive RTP010 Invalid major command RTP011 There was no preceding DB2 command executed RTP012 Error to browse command output, BROWSE RC='&RC RTP013 Line command was not entered but is requited Messages issued by RLX Product Dialogs

RPD010 Specify B - browse table contents or C - display tbl column structure RPD011 Scroll display up/down/left or right or press END to exit RPD012 (A)dd selected column to new table or (C)hange column before adding RPD013 Specify (A)dd, (B)rowse or (T)emplate tbl definition as a row command RPD014 Revise parameters for a NEW table definition and press ENTER RPD015 Browse table definition attributes - press ENTER to continue RPD016 Table definition attributes browsed successfully RPD017 New global table attributes defined successfully RPD018 Specify (A)dd, (B)rowse or (T)emplate in the row selection field RPD020 Use this table definition as a template for a new object RPD021 Define table or view or identify an existing table to clone RPD022 (A)dd selected column to new table or (C)hange column before adding RPD023 Object already exists - choose another table or view name RPD024 Use these column definitions as templates for new column definitions RPD025 Press ENTER to generate DDL or END / RETURN to exit RPD026 Object DDL being tailored - please wait RPD027 Datatypes are I, S, F, D, C, V, LV, G, VG, LVG, DA, T, TS or R RPD028 Review and revise column definitions and press ENTER


RPD030 Specify column attributes and press ENTER RPD031 Column name already defined - specify another column name RPD032 Review and revise column attributes and press ENTER RPD033 Browse column attributes and press ENTER to continue RPD034 Press ENTER to delete column &dctcoln or END to bypass delete RPD034 Delete of column &dtcname was successful' RPD035 Delete of column &dtcname was NOT successful' RPD040 Key an S to select table(s) for index definition RPD041 Key in an S in the selection field to the left of the table name RPD042 Key an S to select index(es) for detailed definition RPD043 Key an A or S in the selection field to the left of the index name RPD044 Specify (A)dd, (C)hange or (D)elete of an index key column RPD045 Specify new key column attributes and press ENTER RPD046 Index key column &dkcseq# already exists - please respecify RPD047 Review and revise index key column attributes and press ENTER RPD048 New index key column with ordinal number of &dkcseq# was ADDed RPD049 Press ENTER to delete index key column or PF3/PF15 to bypass RPD050 Key in an A, C, D or S in the row selection field on the far left RPD051 Clone global index attributes and press ENTER RPD052 (A)dd, (C)hange or (D)elete an index partition definition RPD053 Specify new index partition attributes and press ENTER RPD054 Index partition &dippart# already exists - please respecify RPD055 Review and revise index partition attributes and press ENTER RPD056 Definition for index partition &dippart# was changed successfully RPD058 New definition for index partition &dippart# was added successfully RPD059 Press ENTER to delete index partition &dippart# or PF3/PF15 to

bypass


RPD060 Deletion of index partition &dippart# was bypassed RPD061 Definition for index partition &dippart# deleted successfully RPD062 Delete failed for definition of index partition &dippart# RPD063 Limit key definition applies only to PARTITIONED indexes RPD064 Global attributes for &dciowner..&dciname set successfully RPD065 Define index key columns before generating CREATE INDEX DDL RPD066 Define global index attributes before generating CREATE INDEX

DDL RPD067 Define at least partition 0 attributes before tailoring DDL RPD070 Limit key for Partition &dlkpart# component &dlkcomp# already

exists RPD071 New limit key value was added successfully RPD075 Review and revise index partition attributes and press ENTER RPD073 Limit key value was updated successfully RPD074 Limit key value was deleted successfully RPD075 Delete for Limit key was not successful RPD076 Update limit keys in place or enter Add, Change, Delete row commands RPD080 Key in an A, C or D in the row selection field on the far left RPD081 Specify global index attributes and press ENTER RPD082 (A)dd, (C)hange or (D)elete a limit key definition RPD083 Specify new limit key attributes and press ENTER RPD084 limit key for partition &dlkpart# component &dlkcomp# already exists RPD085 Review and revise limit key attributes and press ENTER RPD086 Limit key value was changed successfully RPD088 Limit key value was added successfully RPD089 Press ENTER to delete limit key value or PF3/PF15 to bypass RPD090 Deletion of limit key was bypassed RPD091 Limit key value was deleted successfully


RPD092 Delete failed for definition of limit key &dlkpart# &dlkcomp# RPD093 Limit key definition applies only to PARTITIONED indexes RPD094 Global attributes for &dciowner..&dciname set successfully RPD095 Define index key columns before generating CREATE INDEX DDL RPD096 Define global index attributes before generating CREATE INDEX

DDL RPD097 Define at least partition 0 attributes before tailoring DDL RPD100 Specify explicit owner and table name or selection criteria RPD101 Specify library and mbr into which SQL CREATE DDL should be

tailored RPD102 File tailoring output library not allocated - Please respecify RPD103 Specify (A)dd, (C)hange, (B)rowse, (D)elete or (S)elect RPD104 Update constraint definitions in place or (S)elect to define columns RPD105 Specify a delete rule of either (R)estrict, (C)ascade or Set (N)ull RPD106 Specify foreign key columns by specifying non zero col sequence #''s RPD110 Define global table attributes before generating CREATE TABLE

DDL RPD111 Define table''s columns before generating CREATE TABLE DDL RPD112 Define table''s attributes and columns before defining foreign keys RPD113 Define table''s attributes and before defining its columns RPD114 No indexes defined for this table - Specify (A)dd row command RPD115 (S)elect table columns for inclusion in the new index RPD116 Specify name and attributes of the new index and press ENTER RPD117 1 or more columns selected for inclusion in new index RPD118 Key an A in the selection field to define a NEW index partition RPD120 Specify constraint attributes and press ENTER RPD121 constraint name already defined - specify another constraint name RPD122 Review and revise constraint attributes and press ENTER RPD123 Browse constraint attributes and press ENTER to continue


RPD124 Press ENTER to delete constraint &dctcoln or END to bypass delete RPD124 Delete of constraint &dfkname was successful' RPD125 Delete of constraint &dfkname was NOT successful' RPD126 &zcmd is NOT a valid option' Messages associated with generic SQL routines PSQ000 RLX statement too big or too complex to process PSQ001 Expected WHERE keyword introducing a search condition was not

found PSQ002 The SQL statement ended prematurely at the flagged token. PSQ003 The &PSQVERB statement ended prematurely at the flagged token. PSQ004 Expected INTO keyword following INSERT verb not found PSQ005 Expected open parenthesis ( commencing a list was not found PSQ006 Expected close parenthesis ) delimiting a list was not found PSQ007 Expression or built in function reference has unbalanced parenthesis PSQ008 Expected keywords CURSOR FOR were not found in SQL DECLARE

statement PSQ009 A nested subselect did not begin with an open parentheis PSQ010 Either table name or table name alias expected in a table name list PSQ011 Null indicator variable reference invalid within a search condition PSQ012 Unsupported datatype for exec variable and corresponding SQL

column PSQ013 The expected INTO keyword was not found in a SQL FETCH

Statement PSQ014 The expected FROM keyword was not found in a SQL DELETE

Statement PSQ015 Expected WHERE or HAVING keyword not found in search condition PSQ016 Expected BY keyword does not follow GROUP or ORDER keyword


PSQ017 Expected cursor name to follow the flagged token PSQ018 Unrecognizable INSERT syntax following column name list PSQ019 INSERTs column name list not delimited by ) PSQ020 Statement executed successfully but exceptional condition occurred PSQ021 Error occurred executing the RLX SQL statement described below PSQ022 Invalid, unrecognizable syntax detected in SELECT statement PSQ023 SQL Verb not recognized - Statement unexecutable PSQ024 SQL statement contains too few tokens for the referenced verb PSQ025 SET keyword within UPDATE statement not found when expected PSQ026 Expected equal sign = within UPDATE SET clause not found PSQ027 Expected column name within UPDATE SET clause not found PSQ028 Unexpected keyword followed UPDATEs SET clause - expected

WHERE PSQ029 FOR UPDATE Of or ORDER BY clause not associated with outer

SELECT PSQ030 Call attach facility error: Return code &PDFRC Reason code

&PDFRRC PSQ031 Cursor name referenced not previously DECLARED PSQ032 Expected UPDATE keyword not found in FOR UPDATE OF clause PSQ033 Expected OF keyword not found in FOR UPDATE OF clause PSQ034 Resources unavailable for &PSQAPN are described by message

DSNT500I PSQ035 Flagged RLX Verb is not implemented - Contact Vendor for more info PSQ036 The singleton SELECT requires an INTO list of host variables PSQ037 Expected ONLY keyword - found flagged token in FOR FETCH

ONLY clause PSQ038 Found illegal statement tokens following FOR FETCH ONLY clause PSQ039 Requested plan &PSQAPN does not exist within DB2 subystem

&RLXDSN PSQ051 DB2 subsystem named &RLXDSN is not active


PSQ052 DB2 subsystem named &RLXDSN does not exist PSQ053 ID &ZUSER is not authorized to use DB2 PSQ054 RLX connection failed because DB2 subsystem &RLXDSN is

terminating PSQ055 Application plan named &PSQPLAN is not valid PSQ056 Your DB2 connection ID is not authorized to use Plan &PSQAPN PSQ057 Maximum connections reached. Attempt DB2 connection later. PSQ058 Task control block not connected to DB2 PSQ059 DB2 connection type parameter is in error PSQ060 DB2 subsystem &RLXDSN is not active PSQ061 CAF control blocks reset successfully - Ready to reconnect PSQ062 CAF CLOSE issued when there was no active OPEN PSQ063 CAF DISCONNECT issued when there was no active CONNECT PSQ064 Release level mismatch between Call Attach Facility and DB2

Subsystem PSQ070 Expected column name within UPDATE SET clause not found PSQ071 Expected equal sign = within UPDATE SET clause not found PSQ072 Expected SET keyword within UPDATE statement not found PSQ073 Ambiguous/unknown host variable datatype PSQ074 Statement too long or complex for describe select processing PSQ075 Select list receiver overflow during describe select processing PSQ076 From list receiver overflow during describe select processing PSQ077 Overflow of the candidate table designator stack PSQ078 Column name qualifier is ambiguous or unknown PSQ079 Select list stack overflow during describe select processing PSQ080 Too many nested SELECTS - statement to complex to process PSQ081 Error occured in trying to identify host input variable datatype(s) PSQ082 Error describing INSERT with implicit column name list


PSQ083 Error describing INSERT with implicit column name list PSQ084 Warning - More host variable values than columns - some ignored PSQ085 Expected keyword VALUES in an INSERT statement not found PSQ086 The flagged token overflowed the dummy SELECT list PSQ087 The flagged token overflowed the FROM reference table PSQ088 No object tables named in this statement PSQ090 Expected PLAN or ALL keyword to follow EXPLAIN verb PSQ091 Expected keyword SET to follow PLAN or ALL in EXPLAIN verb PSQ092 Expected keyword QUERYNO to follow SET in EXPLAIN verb PSQ093 Expected keyword = to follow QUERYNO in EXPLAIN verb PSQ094 Query number identifying EXPLAIN request must have integer value PSQ095 Expected keyword FOR to follow query number in EXPLAIN verb PSQ096 EXPLAIN supported verbs are DELETE, INSERT, SELECT, or

UPDATE PSQ100 SQL Verb type not recognized for canonical transformation processing PSQ101 The referenced cursor is not active vis SQL or RLX - contact vendor PSQ102 Exceeded plan maximum for DELETE, INSERT, or UPDATE

statements PSQ103 Exceeded plan maximum for SELECT or DECLARE statements PSQ104 No row(s) will be updated because of invalid column value PSQ105 No row inserted because column value was invalid for its datatype PSQ106 The referenced cursor name is not prepared and cannot be used PSQ107 Host/indicator variable mismatch between DECLAREd CURSOR and

FETCH PSQ108 Cursor name referenced is not active vis a vis SQL - contact vendor PSQ109 Cursor name referenced is not active vis a vis RLX - contact vendor PSQ110 CONTROL verb request type is neither recognized nor supported PSQ111 Supported CONTROL ERRORS options are CANCEL, FILTER, or

RETURN


PSQ112 Supported CONTROL NUMERIC options are INTEGER, EDITED, or MAXDIGIT

PSQ113 Supported CONTROL SCOPE operands are CURSOR, VARS,and

STATEMENT PSQ114 Supported SCOPE values are LOCAL and GLOBAL PSQ115 Supported EPANEL (Error Panel) options are DISPLAY or

NONDISPL PSQ116 Expected NAMES keyword to follow NUMERIC INTEGER or

EDITED option PSQ117 Expected CODES or DEFAULT keyword to follow CONTROL

ERRORS FILTER PSQ118 Error filter code must be a numeric integer PSQ119 Specify a CONTROL ISPERROR option of either CANCEL or

RETURN PSQ120 DB2 Abend 04E - Your SQL interface task Abend Reason Code is

&PDFRRC PSQ121 DB2 Abend 04F - DB2 subsystem Abend Reason Code is &PDFRRC PSQ122 Error in initializing control blocks for a SQL interface process PSQ123 Unsupported RLX SQL statement type - contact vendor PSQ131 SELECT INTO statement failed - RLX simulated the -811 SQLCODE PSQ132 More receiver host main variables than SQL result columns PSQ133 More SQL result columns than host main variables to receive them PSQ134 :MAIN:INDICATOR:??? is illegal host variable notation PSQ140 Specify an integer limit for the number of rows loaded by ISPFTABLE PSQ141 The LOCAL date/time format is not supported in RLX 1.1 PSQ142 Select date/time format from among ISO, USA, EUR, or JIS - Not

LOCAL PSQ143 Did not find a ) to delimit a list of host variable names PSQ144 Expected the name of a supported data type but found flagged token PSQ145 Keyword LONG appropriate only before VARCHAR or

VARGRAPHIC PSQ146 RLX internal error in attempting to allocate an EVD


PSQ147 Unrecognized or unsupported VDEFINE service keyword PSQ148 Expected an open parenthesis ( to follow keyword and enclose value PSQ149 Expected a close parenthesis ) to follow keyword value PSQ150 Host variable name > 8 characters in INTO clause of DECLARE

ISPFTABLE PSQ151 Expected || concatenation operator or delimited character constant PSQ152 Column name and insert value lists got out of sync before this token PSQ153 Too many levels of nesting for sub query - Simplify your statement PSQ154 Expected SQL built in function reference prior to the flagged token PSQ155 Internal logic error - Unrecognized host variable category PSQ156 Context and usage force an unsupported datatype for flagged variable PSQ157 Incompatible expressions detected in a predicate PSQ158 Illegal predicate of the form :HOST_VARIABLE =

:HOST_VARIABLE PSQ159 Predicate state determination - internal logic error PSQ160 Expected YES or NO for NULLs support for this host variable PSQ161 Length specification invalid for a host variable of this datatype PSQ162 Unexpected end of CONTROL statement - expected value for keyword PSQ163 Expected a comma between Decimal precision and scale values PSQ164 Variable SCOPE must be either LOCAL or GLOBAL PSQ170 Expected Equal Sign = but found flagged token PSQ171 The datatype of the flagged host variable is ambiguous - Try VDEFINE PSQ172 Expected comparison operator, BETWEEN, IS, LIKE, EXISTS, or IN PSQ173 Expected NOT or NULL within an IS predicate - found flagged token PSQ174 Invalid syntax for the LIKE predicate PSQ175 Expected subselect following EXISTS predicate - found flagged token PSQ176 Expected Host variable, constant, or USER for IN predicate list PSQ177 Expected USER, host variable, or string constant as object of LIKE


PSQ178 Predicate expression was expected to end at the flagged token PSQ179 Expected the keyword AND within the context of a BETWEEN

predicate PSQ180 Select 1 or more host variable name(s) for processing with an S PSQ181 Specify DB2 supported datatype or Select row for prompts PSQ182 Specify valid integer value for host variable length PSQ183 Specify valid integer between 1 and 15 for a decimal scaling factor PSQ184 Specify Yes or No whether nulls are allowed PSQ185 Host variables marked R require datatype definition PSQ186 Unknown Host Variable datatype(s) - Statement execution impossible PSQ187 Specify a variable scope of S - Statement, L - Local, or G - Global PSQ188 Exceeded maximum length of name for a Vdefined host variable PSQ189 Host variable name not found PSQ190 Expected NOT or NULL to follow IS predicate - found flagged token PSQ191 Undefined host variables - Define them or press RETURN key to abend PSQ192 Select 1 of the datatype codes A - M from the panel type code list PSQ193 One or 1 of the datatype codes A - M from the panel type code list PSQ195 Specify host variable data type attributes and press ENTER PSQ196 There is no default length for this datatype - please specify PSQ197 Expected an open parenthesis ( to introduce the INSERT value list PSQ198 More host variables in value list than columns in target INSERT table PSQ199 Expected digits to follow period - String constant needs quotes PSQ200 Undefined Host variable datatypes make execution impossible PSQ201 Valid ISPF Table reuse dispositions are EXTEND, DELETE or TEST PSQ202 ISPF Table Name not found - Valid generic names are PERM or

TEMP PSQ210 Specify host variable length within the range 1 thru 32704 PSQ211 Specify character variable length in the range 1 thru 254


PSQ212 Specify graphic variable length in the range 1 thru 16352 PSQ213 Specify graphic variable length in the range 1 thru 127 PSQ214 Specify single precision (length 4) or double precision (length 8) PSQ216 The only valid length for an integer host variable is 4 PSQ217 The only valid length for a smallint host variable is 2 PSQ220 SET statement expected CURRENT keyword PSQ221 SQLID keyword of the SET statement was expected but not found PSQ222 Equal sign = of the SET statement was expected but not found PSQ223 More tokens than permitted by syntax of SET CURRENT SQLID =

token PSQ224 Flagged token is not the name of a valid SQL special register PSQ225 Flagged token is not the name of a SQL CURRENT special register PSQ226 CURRENT PACKAGESET must be SET to :hostvar, USER or a string

constant PSQ227 CONNECTION must be SET to :hostv or string constant (without

quotes) PSQ230 Too many tokens in RLX statement string - * flags token before limit PSQ231 RLXPREF keyword only valid with DECLARE ISPFTABLE

statement PSQ232 RLXPREF keyword requires (value) as in RLXPREF(VAR) PSQ233 Dialog variable name prefix (defined via RLXPREF) limited to 4 chars PSQ234 A SQL FROM clause should follow the INTO RLXPREF(value) clause PSQ240 Set RC or LASTCC to either SQLCODE, NONZERO or ZERO PSQ241 Specify a CONTROL DROP target of STATEMENT or

STATEMENTS PSQ242 Specify a CONTROL REFRESH option of RLXPROF PSQ243 Specify a CONTROL COST option of YES or NO PSQ244 Only the RLXPROF option of RLX CONTROL REFRESH is

supported


PSQ250 Expected FOR keyword not found in OPTIMIZE FOR integer ROWS clause

PSQ251 An integer number for rows is required by the OPTIMIZE clause PSQ252 Expected ROW or ROWS keyword not found in OPTIMIZE clause PSQ253 Expected HOLD keyword not found in WITH HOLD clause PSQ254 Unrecognizable syntax for CONNECT request PSQ255 CONNECT TO syntax requires host var or location name without

quotes PSQ256 Verb requires more tokens than supplied PSQ257 Error detected by Semantic token scan routine PSQPTS PSQ258 An integer number for rows is required by the START_TBADD clause PSQ259 START_TBADD must be the last clause in a DECLARE ISPFTABLE

statement PSQ260 Exceeded plan maximum for DECLARE CURSOR WITH HOLD

statements PSQ261 #BITMAP ON function failed - Internal error PSQ262 #BITMAP OFF function failed - Internal error PSQ263 START_TBADD clause only valid with DECLARE ISPFTABLE

statement PSQ264 Unrecognizable syntax for RELEASE request PSQ265 RELEASE ALL syntax expects either SQL or PRIVATE

RLX/Compile Messages 2-1

RLX/Compile Messages RLX/Compile Run-time messages

RCS000 SQL statement not found within static plan &XCTPLAN RCS020 &RLXPGM specified by the RLXPGM parameter is not an RLX SQL

module

RLX/Compile Dialog Messages RCS010 Select 1 or more RLX source modules for program preparation RCS011 Press ENTER to conduct RLX/Compile IVP (for REXX EXEC

&rcsivpn) RCS050 Revise SQL load module name to be different from compiled REXX

lmod RCS051 Specify 1 or more modules to be bound and link edited together RCS052 Specify 1 or more RLX source modules to be precompiled RCS053 Specify 1 or more RLX request modules whose SQL should be compiled RCS054 Specify REXX Compile / Link Edit options and press ENTER RCS060 RLX/Compile V1.1 does not support hybrid compiled / dynamic plans

2-2 RLX Messages Reference

RCS061 Compiled REXX and compiled SQL load module names MUST be different

RCS062 RLX/Compile V1.1 not yet integrated with REXX compilers RCS070 Specify REXX EXEC(s) to be precompiled, SQL compiled and

AcceleREXXed RCS071 Specify AcceleREXX compile options and press ENTER RCS072 DB2 packages and collections are not supported by this DB2 release RCS073 Specify package BIND attributes for the RLX package collection RCS074 RLX package BIND jobstream processed sucessfully RCS075 Please wait while PACKAGE BIND control statements are tailored RCS076 Please wait while DB2 PACKAGE BIND jobstream is tailored RCS080 Specify BIND attributes for the RLX multi-plan application plans RCS081 Please wait while multiple plan BIND control statements are tailored RCS082 Please wait while multi-plan BIND jobstream is tailored RCS083 RLX multi-plan BIND jobstream processed sucessfully RCS120 Press ENTER to tailor RLX/Compile jobstream or END to bypass RCS121 Verify RLX/Compile jobstream specifications or press END to bypass RCS123 Please wait while RLX/Compile data structure is tailored RCS124 Please wait while jobstream to process &mslcount members is tailored

RLX/Compile Adminstrative Messages RCS200 Specify RLX/Compile Installation Parameters and press ENTER RCS201 Verify RLX/Compile library names and press ENTER RCS202 RLX/Compile parameters updated successfully RCS203 Specify RLX and DB2 system load libraries and press ENTER RCS204 Specify Job and Jobparm values for RLX/Compile and press ENTER RCS205 Specify the names of AcceleREXX system and user libraries RCS206 AcceleREXX is now integrated into the RLX/Compile environment

RLX/Compile Messages 2-3

RCS207 Revise high level qualifiers of RLX/Compile libraries and press ENTER RCS208 RLX/Compile library names updated successfully RCS209 Verify user output libraries written by your REXX compiler RCS211 Specify high level qualifiers of RLX/Compile libraries RCS212 RLX/Compile User library names updated successfully RCS213 RLX/Compile User libraries will be allocated on volume &rluvol


RLX/CAF Messages and Codes 3-1

RLX/CAF Messages and Codes

RLX/CAF provides extensive and consistent error diagnostics. Error codes are communicated to calling programs through both a Return Code (Register 15) and SQLCODE. RLX/CAF sets the Return Code and SQLCODE with identical values for developer convenience and to avoid ambiguity. SQLCODE values are documented in the "IBM DATABASE 2 Messages and Codes" manual. Codes unique to RLX/CAF are in the -100000 range so as not to conflict with DB2's values for SQLCODE. In addition, RLX/CAF provides error messages, as appropriate, to elucidate the codes and assist in diagnostics. RLX/CAF error messages are prefixed by the letters 'CAF'.

1.1 Abend Codes RLX/CAF issues deliberate User abends under certain conditions. In the event of these abnormal conditions, you should open a problem with RAI Technical Support. Some of these abend codes are: U2001 An internal logic error in which RLX/CAF failed to detect an RAI

Reusable Function Architecture (RFA) environment. U2002 An internal logic error in which RLX/CAF detected a Dynamic

Save Area (DSA) stack overflow.

U2003 Abend issued in response to ABEND CAF RLX/CAF API RLX/CAF.


1.2 Messages 1.2.1 General RLX/CAF messages CAF100E RLX/CAF logic error, initialization failed Explanation This message is issued when a critical RLX/CAF initialization error

occurs. RLX/CAF execution is aborted. Developer Response Determine the reason for error by examining other messages. If unable

to determine a reason for error obtain RFATRACE and notify RAI. CAF102E Thread was not specified on call < CMBFUNC > Explanation An invalid parameter was specified on the RLX/CAF service request

call_ name. Developer Response Verify call syntax. CAF103E Invalid function passed on API call Explanation The service name is not correct. Developer Response Check the coding of the RLX/CAF call. Verify the service name is

mapped into a 12 byte character field, padded with spaces. Refer to Chapter 3 for correct API call names.

Problem Determination Probable user error. If problem persists, obtain an RFATRACE listing

and call RAI. CAF104E Invalid thread handle passed on API call < CMBFUNC > Explanation See message text. Developer Response None. CAF105E GETMAIN failed when creating thread block Explanation See message text. Developer Response Increase the REGION size on the JCL EXEC statement and rerun the

job. Problem Determination If problem persists, obtain an RFATRACE listing and call RAI.


CAF106E DD name <ddname> on API call CR_THREAD was not allocated Explanation The file named <ddname> was not allocated in the JCL.

CREATE_THREAD thread API call LOAD(<ddname>) parameter specifies a DDNAME which is not allocated in the JCL.

Developer Response Allocate the <ddname> file in your JCL and rerun the job. CAF107E Create dynamic DCB failed Explanation An internal RLX/CAF logic error occurred. Developer Response Report problem to RAI CAF108E Open for DD name <ddname> failed Explanation Open failed while opening DD statement <ddname>. Locate related

IEC.... message(s) to determine cause of open failure. Developer Response Examine attributes of data set allocated to <ddname>. There may be a

problem with the data set or an I/O error may have occurred against the dataset device.

Problem Determination Correct problem with data set and rerun the job. CAF111E Create CAFD process failed Explanation An ATTACH macro has failed to create a TCB for RLX/CAF data

task. This is an internal RLX/CAF error. Developer Response Obtain an RFATRACE listing and SYSUDUMP and notify RAI. CAF112E Invalid thread handle < thread_id > Explanation The thread handle thread_id passed on an API call was not a valid. Developer Response Find message CAF902I related to the thread in question. Make sure

the value of the thread host variable matches that of thread_id. Problem Determination Probable programming error. If unable to determine cause of an error

obtain RFATRACE and call RAI. CAF113E Unknown event detected by CAF scheduler Explanation RLX/CAF has encountered a logic error. Developer Response Obtain RFATRACE, SYSUDUMP, Job log. Call RAI.


CAF114I RLX/CAF START successfully executed Explanation Informational message Developer Response None Problem Determination None CAF115I RLX/CAF STOP successfully executed Explanation An informational message Developer Response None Problem Determination None CAF116E Failed to load CAF$R31 module Explanation The load module named CAF$R31 was not found. Developer Response Check that the CAF$R31 load module is in a load library searched by

OS. Check if LOAD(dd_name) parameter was specified at run-time. If it was specified then make sure it is allocated.

CAF117E Failed to load CAF$TPD module Explanation Load module CAF$TPD was not found in any of the OS searched load

libraries. Developer Response Check that the CAF$TPD load module is in a load library searched by

OS. Check if LOAD(dd_name) parameter was specified at run-time. If it was specified then make sure it is allocated.

CAF118E Failed to initialize file for output messages Explanation A message output file -- MSGDD(dd_name) file was not successfully

initialized. Developer Response Check file attributes. If unable to determine error, then obtain

RFATRACE and call RAI. CAF119I START already successfully performed, command ignored Explanation An informational message Developer Response None


CAF120I Error count exceeded, CAF issues user abend Explanation An error count specified by DIAGLIM(integer) parameter was

exceeded and ERROR(ABEND) was coded. Developer Response Check errors issued by RLX/CAF. Correct the problem and rerun the

job. CAF121I Error code <sqlcode> while processing SQL statement <sql_stmt> Explanation An informational message - see message text. Developer Response Correct SQL error and rerun the job. CAF122E Failed to open <rtp_dd> DD statement Explanation The open of the Run-time parameters file named rtp_dd failed. rtp_dd

should correspond to either the CAFINPUT, SYSTSIN, DB2BATCH, or SQLBATCH DD statements.

Developer Response Find related IEC... messages pertaining to the open failure. Verify the

dataset is allocated to rtp_dd statement. CAF123E Unknown source of run-time command Explanation RLX/CAF has encountered a logic error. Developer Response Obtain RFATRACE, SYSUDUMP, Job log. Call RAI. CAF124E RLX/CAF initialization error - abend U2003 will be issued Explanation RLX/CAF initialization has failed. A user abend will be issued to force

program termination. Developer Response Find related error messages to determine cause of failure. Rerun the

job when the problem is corrected. CAF125E RLX/CAF invalid or expired product password - contact RAI Explanation See message text. CAF126E RLX/CAF termination control was requested while explicit stop was issued Explanation See message text.


CAF013W - Failed to identify DB2 application thread - CAF stmt syntax error Explanation You issued a CAF command while there was no active DB2 application

thread established. The command failed and the RC variable is set to 130 to indicate a message ID that describes the error,

Developer Response Make sure to connect to a DB2 subsystem before issuing other CAF

commands. 1.2.2 CONNECT, DISCONNECT, OPEN and CLOSE messages CAF201E RLX/CAF CLOSE issued when there was no successful OPEN Explanation See message text. Developer Response Check program logic to see why CLOSE was issued. CAF202E RLX/CAF DISCONNECT issued when there was no successful CONNECT Explanation See message text. Developer Response Check program logic to see why DISCONNECT was issued. CAF203E RLX/CAF control blocks reset successfully - ready to re-CONNECT Explanation This message issued after successful SET command. Developer Response None. CAF204E DB2 subsystem = < DB2_subsystem > is not active Explanation Attempt to connect to DB2_subsystem was unsuccessful. The

subsystem is not active. Developer Response Check if DB2_subsystem is valid. If valid then activate it. CAF205E DB2 subsystem = < DB2_subsystem > was not defined Explanation The subsystem named DB2_subsystem is not defined. Developer Response Verify the DB2 subsystem name and rerun the job.


CAF206E DB2 connection type parameter is in error Explanation This is probably RLX/CAF logic error. Developer Response Report problem to RAI. CAF207E User ID is not authorized to use DB2 Explanation See message text. Developer Response Verify whether user id is authorized to use DB2. CAF208E Task Control Block not connected to DB2 Explanation This error is the result of an unsuccessful CONNECT call. Check

CAF901E message for DSNALI return and reason code. Developer Response Check 'DB2 Messages and Codes' for return and error codes. CAF209E Connection failed - DB2 = < dsn > is terminating Explanation See message text. Developer Response Check DSNALI return and reason code on message CAF901E CAF210E Application plan = < plan > is not valid Explanation The application plan named plan was not successfully bound into the

current DB2 subsystem. Developer Response Correct plan name and retry operation. CAF212E Maximum connections reached, attempt DB2 connection later Explanation CONNECT to DB2 failed. RLX/CAF attempted the number of

connection retries specified or defaulted by the RETRY(integer) parameter.

Developer Response Retry operation later when the DB2 subsystem is available. CAF213E CAF DB2 Release level mismatch Explanation An attempt was made to connect to a DB2 V2.3 subsystem while the

DSNALI module was loaded from a DB2 V2.2 load library.

Developer Response Verify LOAD(name) parameter or STEPLIB DD statement of your job.


CAF214E Application plan=plan is not authorized for this user ID Explanation See message text. Developer Response Make sure a user id is authorized to use application plan. CAF215E Resource unavailable Explanation See message text. Developer Response Find related message CAF901E, and diagnostic messages which will

further describe the problem. CAF216E CONNECT to DB2 subsystem failed - critical error - no retries will be attempted Explanation See message text. Developer Response See related RLX/CAF messages for reason of CONNECT failure. CAF217E Failed to CONNECT to DB2 subsystem, halt connection retries Explanation See message text. Developer Response See related message CAF902I. CONNECT to DB2 subsystem failed,

connection retries initiated and exceeded. Start DB2 subsystem and retry failed operation.

CAF218E RLX/CAF DISCONNECT command failed Explanation See message text. Developer Response See related RLX/CAF messages for reason for DISCONNECT failure. CAF219E RLX/CAF OPEN plan failed - TRANSLATE was issued Explanation See message text. Developer Response TRANSLATE was issued to convert DSNALI return and reason codes

to SQLCODE. See related RLX/CAF messages for an explanation of the error.

CAF220E RLX/CAF CLOSE application plan failed Explanation See message text. Developer Response See related RLX/CAF messages for the reason for CLOSE failure.


CAF221E RLX/CAF OPEN application plan failed - TRANSLATE was not issued Explanation OPEN command failed with reason code 8. This error code could not

be translated. Developer Response See related CAF901E message for return and reason code from

DSNALI. 1.2.3 Error messages related to application thread CAF301E RLX/CAF scheduler abended < abend_code > Explanation System abnormal termination was detected in RLX/CAF ESTAE exit

while executing RLX/CAF code. Developer Response Obtain SYSUDUMP, JCL, and Job Log of abending job. Report

problem to RAI. CAF302E Invalid function passed to thread Explanation A logic error within RLX/CAF. Developer Response Obtain RFATRACE and report problem to RAI. CAF303W RLX/CAF CONNECT request issued for already connected thread, request ignored Explanation See message text. Developer Response Examine your program to see why CONNECT is attempted for an

already connected thread. CAF304E RLX/CAF DISCONNECT request issued when thread was not connected Explanation See message text. Developer Response See CAF303W message.


CAF305W RLX/CAF OPEN request issued for already opened thread, request ignored Explanation See message text. Developer Response See CAF303W message. CAF307W RLX/CAF CLOSE issued for thread which was not open, request ignored Explanation See message text. Developer Response See CAF303W message. CAF309E Failed to open DD name = < load_dd > Explanation See message text. Developer Response Failed to open DB2 load library DD load_dd which was specified on

CREATE command or in CAFINPUT file. Make sure load_dd was allocated and have correct dataset names.

CAF310E Failed to locate DSNALI, DSNHLI2 or DSNWLI Explanation See message text. Developer Response Failed to locate one of the DB2 modules in the load library or

STEPLIB. Make sure the correct STEPLIB or LOAD libraries are allocated.

CAF312E DB2 subsystem < dsn > was quiesced by the operator Explanation DB2 subsystem was quiesced while a job under RLX/CAF control was

performing a SQL call. Developer Response Rerun the job. CAF313E Error received from RFARPR Explanation Run-time parameters parser encounter a parameter with incorrect

syntax. Developer Response See related RLX/CAF messages for specific error. CAF314E Thread was terminated by DB2 Explanation See message text.


Developer Response Check system log to determine a reason for thread termination. CAF315E Error while linking to user plan exit < plan_exit > Explanation A PLANEXIT(plan_exit) parameter was defined in CAF$TPD or on

CAFINPUT file but load module plan_exit could not be loaded from STEPLIB or load library.

Developer Response Make sure that plan exit module was link-edited into a load library

accessible to the jobstep. CAF316W Connection to DB2 aborted by user exit < plan_exit > Explanation A user plan_exit requested the connection to DB2 be aborted. Developer Response This is a result of your request to abort a DB2 connection. CAF317W Invalid action flag returned by user plan exit Explanation See message text. Developer Response User plan exit returned an invalid flag in the communication DSECT.

Check your plan exit code. CAF318E RLX/CAF thread abended < abend_code > Explanation See message text. Developer Response An abend occurred while executing an SQL call. Save SYSUDUMP

and report problem to RAI. CAF319E Timeout occurred while waiting for response from DB2 or thread abended Explanation See message text. Developer Response The timeout interval established by the TIMEOUT(value) parameter

was exceeded. Application probably was in a wait due to a resource unavailable condition. Examine job log for other messages which could explain the problem. Adjust DSN2PARM timeout parameter or increase the TIMEOUT value.

CAF320I Console command processed Explanation A command entered from system console was processed.


Developer Response None. CAF321I Termination caused by attention request Explanation An attention request (MVS STOP command) caused termination. Developer Response None. CAF322I Thread successfully terminated Explanation See message text. Developer Response None. CAF323E Failed to load DSNTIAR Explanation See message text. Developer Response Check STEPLIB or LOAD library. CAF324E SET command failed, thread is not IDLE Explanation See message text. 1.2.4 Informational messages related to application threads CAF351I RLX/CAF CR_THREAD successfully executed Explanation See message text. Developer Response None. CAF352I RLX/CAF RM_THREAD successfully executed Explanation See message text. Developer Response None. CAF353I RLX/CAF CONNECT successfully executed Explanation See message text. Developer Response None


CAF355I RLX/CAF DISCONNECT successfully executed Explanation See message text. Developer Response None CAF356I RLX/CAF OPEN successfully executed Explanation See message text. Developer Response None CAF357I RLX/CAF CLOSE successfully executed Explanation See message text. Developer Response None CAF358I RLX/CAF SWITCH successfully executed Explanation See message text. Developer Response None CAF359I RLX/CAF QUERY successfully executed Explanation See message text. Developer Response None CAF360I RLX/CAF SNAP successfully executed Explanation See message text. Developer Response None CAF363I RLX/CAF ACTIVATE successfully performed Explanation See message text. Developer Response None CAF364I RLX/CAF SET successfully performed Explanation See message text. Developer Response None


1.2.5 Command parser messages CAF401E Error while translating command to uppercase Explanation An internal error within RLX/CAF. Developer Response Notify RAI. CAF402E Error while performing physical token scan Explanation An internal error within RLX/CAF. Developer Response Notify RAI. CAF403E Invalid keyword detected; parse aborted Explanation See message text. Developer Response Check related error message for a specific error. CAF404E Invalid thread variable - must be a host variable Explanation See message text. Developer Response Correct parameter and rerun the job. CAF405E Invalid token Explanation See message text. Developer Response Check related error message for a specific error. CAF406E Invalid verb found; parse aborted Explanation No valid parameter was found in command being described. Developer Response Correct parameter and rerun the job. CAF407E Keyword CAF missing; parse aborted Explanation See message text. All commands must start with 'CAF' verb. Developer Response Correct command and rerun a job. CAF408E Required keyword THREAD is missing Explanation See message text. Developer Response Specify THREAD parameter in the command call and rerun the job.


CAF409E Required keyword DSN is missing Explanation See message text. Developer Response Specify DSN parameter in the command call and rerun the job. CAF410E Required keyword PLAN is missing Explanation See message text. Developer Response Specify PLAN parameter in the command call and rerun the job. CAF411E Not enough CAFDA entries allocated Explanation See message text. Developer Response Allocate at least 5 CAFDA entries. CAF412E DESCRIBE requires CAFDA parameter - absent Explanation See message text. Developer Response Specify CAFDA on a call and rerun a job. CAF413E No parameters passed Explanation There were no parameters specified in the command. Developer Response Correct command and rerun the job. CAF414E Invalid CAFDA: CAFDID is not as expected Explanation See message text. Developer Response You must specify 'CAFDA' in the first 8 bytes of the CAFDA. CAF415E Duplicate parameter - command aborted Explanation A duplicate parameter was specified in a command. Developer Response Correct command and rerun the job.


CAF416I DESCRIBE successfully executed Explanation See message text. Developer Response None. CAF417I EXECUTE successfully performed Explanation See message text. Developer Response None. CAF418I Invalid CAFDA: Unknown CAFDFUNC Explanation A CAFDA returned by a DESCRIBE call or built manually contains an

invalid CAFDFUNC code. Developer Response If CAFDA was built by you then verify CAFDFUNC code. If

CAFDA was built by the DESCRIBE command, report problem to RAI.

CAF419I Invalid CAFDA: Unknown CAFDVTYPE Explanation A CAFDA returned by a DESCRIBE call or built manually contains

an invalid CAFDVTYPE code. Developer Response If CAFDA was built by you then verify CAFDVTYPE code. If

CAFDA was built by the DESCRIBE command, report problem to RAI.

CAF420I Invalid keyword value Explanation The value of a parameter was not as expected. e.g. DIAGLIM(integer) expects an integer value. Developer Response Correct parameter value and rerun the job.


1.2.6 Run-time parameters parser messages CAF500E RLX/CAF Run-Time Parameters Read from <rlt_dd> DD statement Explanation See message text. Developer Response None. CAF501E Invalid run-time parameter <rtp_parm> Explanation An invalid run-time parameter rtp_parm was found on CAFINPUT Developer Response Correct parameter and rerun a job. CAF502E Unknown token, expected parameter value Explanation An invalid token was found following a valid parameter -- e.g. a left or

right parenthesis was expected but not found on CAFINPUT. Developer Response Correct parameter and rerun a job. CAF503E Unknown token, expected right parenthesis or end of command line Explanation See message text. Developer Response Correct command and rerun a job. CAF504E Invalid value, RETRY(integer) parameter requires integer value Explanation See message text. Developer Response Correct command and rerun the job. CAF505E Invalid value, ESTAE(YES/NO) parameter allows only YES or NO values Explanation See message text. Developer Response Correct command and rerun the job. CAF506E Invalid value, ERROR(RETURN/ABEND) parameter allows only RETURN or ABEND values Explanation See message text. Developer Response Correct command and rerun a job.


CAF507E Invalid value, USER(YES/NO) parameter allows only YES or NO values Explanation See message text. Developer Response Correct command and rerun a job. CAF508E Invalid value, DIAGCNTL(YES/NO) parameter allows only YES or NO values Explanation See message text. Developer Response Correct command and rerun a job. CAF509E Invalid value, DIAGLIM(integer) parameter requires integer value Explanation See message text. Developer Response Correct command and rerun the job. CAF510E Invalid value, TERMCNTL(YES/NO) parameter allows only YES or NO values Explanation See message text. Developer Response Correct command and rerun the job. CAF511E Invalid value, ROUTCDE(1-16) parameter requires integer value 1 to 16 Explanation See message text. Developer Response Correct command and rerun the job. CAF512E Invalid value, TIMEOUT(integer) parameter requires integer value Explanation See message text. Developer Response Correct command and rerun the job. CAF513E Invalid value, TRACE(YES/NO) parameter allows only YES or NO values Explanation See message text. Developer Response Correct command and rerun the job.


1.2.7 General purpose application thread messages CAF901I CAF error:

RC = < dsnali_rc > REASON CD = < dsnali_reason_cd > Explanation A general error message was issued after unsuccessful OPEN, CLOSE,

CONNECT and DISCONNECT calls. Developer Response Check <dsnali_rc> and <dsnali_reason_cd> for meaning. See if

there were other RLX/CAF messages issued. CAF902I Thread = < thread_id> DB2 = < dsn> Plan = < plan_name > Explanation A general message which will accompany other messages related to a

specific thread. Developer Response None.


RLX/SDK Messages 4-1

RLX/SDK Messages These messages are issued by Software Developer Kit (SDK) which is a part of RLX products portfolio. Users of RLX products may see these messages issued as they develop REXX programs while using RLX/SDK. These messages are also issued by RAI developed software packages, such as Smart/MONITOR which is a component of Smart Jobstream Series, Host/EDIT and others. The Info(I), Debug(D) and Warning(W) level messages will not be displayed unless you use SDKPARM(‘MSGDISP’,opt) to specify message output volume TERSE, VERBOSE or DEBUG. See RLX/SDK User Guide RLX-101-6 for detail description of SDKPARM function. By default no messages other then E-level will be displayed. The latter are always issued to signify a serious problem and are directed to WTO.

SDK001I REXX environment successfully initialized Explanation: You are using RFPH2R and COB2REXX services to invoke a REXX

exec from a High Level Language or COBOL. REXX environment was successfully established

Developer Response: None. Operator Response: None Problem Determination: Normal condition SDK002E REXX environment initialization failed, IRXINIT RC = &RC, REASON = &REASON Explanation: You are using RFPH2R and COB2REXX services to invoke a REXX

program from a High Level Language or COBOL. The IRXINIT invocation (REXX environment initialization service) failed with return code &RC and reason code &REASON. Refer to TSO/E REXX Reference SA22-7790 for explanation of the return and reason code.

Developer Response: Contact your systems programmer Operator Response: None Problem Determination: Review IBM documentation to identify the problem. Contact RAI

technical support


SDK003E Unable to locate REXX exec &EXECNAME in library allocated to DDNAME

&DDNAME Explanation: You are using RFPH2R and COB2REXX services to invoke a REXX

program from a High Level Language or COBOL. The REXX programc &EXECNAME you requested to execute was not found in a library allocated to the DDNAME &DDNAME.

Developer Response: Check library allocated to a &DDNAME to verify that the REXX

program &EXECNAME is indeed located in this library Operator Response: None Problem Determination: If &EXECNAME is in the library contact RAI technical support.

Otherwise specify library where sought REXX program actually resides.

SDK004E RAI APF facility is not installed. Refer to RLX Installation Manual for instructions Explanation: The SDK function you invoked requires to execute APF authorized but

you did not start RAI Server address space which provides APF authorization to the function.

Developer Response: Contact you systems programmer Operator Response: None Problem Determination: Install, configure and activate RAI server address space. SDK005E Function requires parameters -- none specified Explanation: This message may be issued for any SDK function that requires

parameters to operate while you did not specify any parameters Developer Response: Review REXX function parameters, correct the error Operator Response: None Problem Determination: None SDK006E Storage obtain for key 7 failed Explanation: You called SDKDSNU SDK function. The STORAGE OBTAIN for

virtual storage in the protect key 7 had failed. Developer Response: None Operator Response: None Problem Determination: Report this problem to RAI technical support


SDK007E Abend while executing DSNUTILB. Make sure that RLXLOAD is DD name

containing all APF authorized libraries Explanation: You called SDKDSNU SDK function. DSNUTILB program was

loaded from library concatenation which contains non-APF authorized libraries.

Developer Response: None Operator Response: None Problem Determination: Make sure that RLXLOAD library is APF authorized or in the

LINKLIST. If RLXLOAD DDNAME is allocated make sure that all libraries in the concatenation are APF authorized

SDK008E GETMAIN failed to obtain EVALBLOCK, &RC for result area length &REASON Explanation: You are using RFPH2R and COB2REXX services to invoke a REXX

program from a High Level Language or COBOL. The GETMAIN request to obtain virtual storage for a REXX evaluation block had failed with return code &RC and reason code &REASON.

Developer Response: Review ‘RETURN value’ or ‘EXIT value’ statements in the REXX

program you invoked to make sure that the ‘value’ you are trying to return to a calling program is of a reasonable size.

Operator Response: None Problem Determination: None SDK009I RAI REXX Interface is terminating Explanation: You are using RFPH2R and COB2REXX services to invoke a REXX

exec from a High Level Language or COBOL. The REXX program had finished execution and the REXX environment was successfully terminated

Developer Response: None Operator Response: None Problem Determination: Normal condition


SDK010I REXX environment block was located Explanation: You are using RFPH2R and COB2REXX services to invoke a REXX

exec from a High Level Language or COBOL. The IRXINIT call was issued but REXX environment was already active and no new environment was created. The located REXX environment will be used.

Developer Response: None Operator Response: None Problem Determination: Normal condition SDK011E Function parameter &pname number &pnum was omitted but is required Explanation: This message may be issued for any SDK function that requires

parameters. In the message text &pname is the name of a parameter as documented in the RLX/SDK User Guide and &pnum is the parameter order in the parameter list starting from 1.

Developer Response: Review RLX/SDK User Guide to ensure that the function parameters

are correct Operator Response: None Problem Determination: None SDK012E Function parameter &pname number &pnum is of an excessive length Explanation: This message may be issued for any SDK function that requires

parameters. In the message text &pname is the name of a parameter as documented in the RLX/SDK User Guide and &pnum is the parameter order in the parameter list starting from 1. Make sure that listed parameter is of a length required by the function syntax


are correct Operator Response: None Problem Determination: None SDK013E Function parameter &pname number &pnum has non &ptype value Explanation: This message may be issued for any SDK function that requires

parameters. In the message text &pname is the name of a parameter as documented in the RLX/SDK User Guide and &pnum is the parameter order in the parameter list starting from 1. Make sure that listed


parameter is of a type &ptype which can be DECIMAL, PACKED or FLOAT.


are correct and of a required data type Operator Response: None Problem Determination: None SDK014E Function with profile &code aborted for user &user by Server &servername with

RC=&rc Explanation: This message may be issued for any SDK function that was protected

by access profile as defined in the RAI Server Installation and Operations Guide RSV-001-4, Chapter 4 RAI Authorization Facility.

A &code will be one of the codes described in the Chapter 4, e.g. XMEM, XMUP, etc. A &user is a RACF user ID that requested a protected function. A &servername is the name of RAI Server (such as RAI0) that received the authorization request and denied it with return code of &rc (#SAF macro). Possible return codes are:

04 User is not authorized to use requested function 08 Component &code was not defined 12 The ACEE (RACF control block) for the &user was not found Developer Response: None Operator Response: None Problem Determination: Refer to RAI Server Installation and Operations Guide RSV-001-4,

Chapter 4 RAI Authorization Facility for explanation. Review security product definitions: RACF, TOPSECRET, ACF2. Review RAI product Installation Guides for required security profiles and make sure these profiles are defined and authorized users were granted access to these profiles.


RLX/VSAM Messages 5-1

RLX/VSAM Messages

This section lists the messages that RLX/VSAM may issue to notify an application programmer of internal events. Messages are grouped into Informational, Warning or Error classifications with the last letter of the message ID designating its class: I, W or E. Messages are listed in ascending order and are largely self explanatory. Message groups fall in three categories: Terse, Verbose, or Debug – corresponding to message levels E-error, I=Information and D=Debug. This represents the message group level you can select through the RVMSG service, described in Section 1.6.5. Some messages are self explanatory, while others are augmented with additional text. Variables in the message text are preceded by an ampersand character (‘&’). The following conventions apply concerning variable names: &ddname always refers to the name of the file to which a referenced VSAM dataset is allocated

&macrc refers to a return code from an RLP based VSAM macro instruction. A brief description of these codes can be found in section 1.7

&rplopts are valid RPL options listed in section 1.4


TVR001E VSAM OPEN error for file &ddname Explanation Open failed for VSAM file with &ddname. This message is always

accompanied by TVR008E and TVR058E which explain the open error TVR002E Attempt to build ACB for &ddname has failed Explanation VSAM GENCB macro failed while building an ACB. Possible memory

shortage or program logic error. TVR003E A VSAM OPEN was issued without a successful preceding #VACB' Explanation RLX/VSAM initialization error - VCT is not found. TVR004E File &ddname must be allocated prior to making a VSAM request. TVR005E Duplicate VFB found for file &ddname Explanation Logic error. TVR006E MACRF keyword &&DDKWD was not found in ACB keyword table. Explanation Logic error. TVR007E Attempt to build RPL for &ddname has failed. Explanation GENCB macro return code is non-zero R15. TVR008E An OPEN for file &ddname returned a non zero return code. Explanation This message always appear with TVR001E and TVR058E TVR009I VSAM file &ddname was successfully opened. TVR010E A TESTCB indicates an OPEN failure for file &ddname. Explanation TESTCB detected non-zero reason code while open R15 was zero. TVR011E An OPEN was issued for an invalid VFB. Check DDNAME. Explanation Open request issued for DDNAME which is not known to

RLX/VSAM. TVR012E MACRF keyword &rplopt is not permitted in RFA VSAM.


TVR013W RTFA$TVR has not been loaded by RMD function. Assuming VCON access only. Explanation Make sure that RLX/VSAM load library is allocated to a STEPLIB or

ISPLLIB if running in TSO/ISPF environment. TVR014E A PUT was issued for an invalid VFB. Check DDNAME. Explanation An RVPUT call was issued with invalid &ddname parameter. TVR015E A PUT request was the first VSAM IO call. OPEN must be issued first. Explanation RVOPEN must be a first call issued for any VSAM &ddname TVR016E OPTCD keyword &rplopts was not found in RPL keyword table. Explanation Make sure that &rplopts is valid option listed in Section 1.4. TVR017E OPTCD keyword &rplopts is not permitted in RFA VSAM GET/PUT call Explanation A &rplopts is not permitted for specified VSAM file type and operation TVR018E Output record size requested is larger than the catalog maximum TVR019E Both application requested record size and catalog record size are zero TVR020E A MODCB macro for file &ddname failed during PUT processing Explanation Check OPTCD for invalid option combinations TVR021E A PUT for file &ddname was unsuccessful TVR022E An IO error was encountered while performing a PUT for file &ddname. TVR023E A SHOWCB macro was unsuccessful in retrieving control block information

following a PUT for file &ddname TVR024I VSAM return code from RVPUT = &macrc TVR025E A VSAM CLOSE was issued without a successful preceding #VOPEN.


TVR026E An CLOSE was issued for an invalid VFB. Check DDNAME. Explanation Verify that &ddname is valid DDNAME of successfully opened

VSAM file TVR027E VSAM CLOSE error for file &ddname. TVR028E An CLOSE for file &ddname returned a non zero return code. TVR029I VSAM file &ddname was successfully closed. TVR030E A GET request was the first VSAM IO call. OPEN must be issued first. TVR031E A #VGET was issued for an invalid VFB. The DDNAME specified was not found to

be in an OPEN status. TVR032E Input record size requested is larger than the catalog maximum. TVR033E A MODCB macro for file &ddname failed during GET processing. TVR034E A GET for file &ddname was unsuccessful. TVR035E An IO error was encountered while performing a GET for file &ddname TVR036E A SHOWCB macro was unsuccessful in retrieving control block information

following a GET for file &ddname. TVR037I VSAM return code from RVGET = &macrc TVR038E Detected an attempt to GET a record after an end of file indication was already

presented for file &ddname. TVR039E End of file encountered for file &ddname Explanation An attempt was made to sequentially access a file beyond end-of-file. TVR040E MODCB failure for file &ddname in #VACB routine. Explanation VSAM MODCB macro has failed. Possible program logic error.


TVR041E A REXX RV... function has completed unsuccessfully. TVR042E An attempt to issue a #VACB macro has failed. Explanation Internal ACB creation process failed. Logic error. TVR043E A #VOPEN macro failed processing file &ddname. TVR044I A #VOPEN was successful for file &ddname. TVR045E A #VCLOSE macro failed processing file &ddname. TVR046I A #VCLOSE was successful for file &ddname. TVR047E No IOAREA was specified in a RV... VSAM call. Explanation IO area was a required parameter on this RLX/VSAM function call. TVR048E Invalid RV... function parameter specification. Explanation Verify RLX/VSAM function call syntax in Section 1.6. TVR049E Unsuccessful RV... macro call. TVR050I File &ddname completed without explicitly specifying OPTCD. Explanation &rplopts previously set or defaulted have been used in this call. TVR051I A VPUT request has specified an OPTCD override. TVR052I A VGET request has specified an OPTCD override. TVR053I A VPOINT request has specified an OPTCD override. TVR054I A #VGET for file &ddname is making use of default RPL OPTCD options. TVR055I A #VPUT for file &ddname is making use of default RPL OPTCD options.


TVR056I VSAM reason code from RVPUT = &macrc Explanation Refer to section 1.7 for a list of error return codes. TVR057I VSAM reason code from RVGET = &macrc Explanation Refer to section 1.7 for a list of error return codes. TVR058I VSAM return code from OPEN = <Rc> Explanation VSAM open macro has failed. <Rc> is a content of R15 at the time of

error. TVR059I VSAM reason code from OPEN = <ReasonCode> Explanation VSAM open macro has failed. Refer to Section 1.7 Open reason codes

for error details. TVR060I VSAM return code from CLOSE = &macrc Explanation Refer to section 1.7 for a list of error return codes. TVR061I VSAM reason code from CLOSE = &macrc Explanation Refer to section 1.7 for a list of error return codes. TVR062E A GET was issued with MVE mode active but no IOAREA defined. Explanation MVE option is not supported in RLX/VSAM TVR063W A LOC mode GET was issued. IOAREA will be ignored. TVR064I A #VPOINT for file &ddname is making use of default RPL OPTCD options. TVR065E A MODCB macro for file &ddname failed during POINT processing. TVR066E A POINT for file &ddname was unsuccessful TVR067I VSAM return code from POINT = &macrc TVR068I VSAM reason code from POINT = &macrc


TVR069E An ERASE was issued for an invalid VFB. Check DDNAME. TVR070E An POINT was issued for a an invalid VFB. Check DDNAME. TVR071I VSAM return code from ERASE = &macrc TVR072I VSAM reason code from ERASE = &macrc TVR073E An ERASE for file &ddname was unsuccessful TVR074E An IO error was encountered while performing an ERASE for file &ddname. TVR075E Unknown VSAM file type detected. Notify RAI. TVR076E Unknown VSAM file type returned from TESTCB. Notify RAI. Explanation VSAM file type specified in &ddname on RVOPEN call is of incorrect

type not KSDS, ESDS, RRDS, or LDS. TVR077W RPL OPTCD of MVE has been overlaid with LOC. RVGET continuing. TVR078E Unable to override MVE OPTCD. Check RVGET option string. TVR079E A VERIFY was issued for an invalid VFB. Check DDNAME. TVR080E A MODCB macro for file &ddname failed during VERIFY processing. TVR081E A VERIFY for file &ddname was unsuccessful TVR082I VSAM return code from VERIFY = &macrc TVR083E An IO error was encountered while performing a POINT for file &ddname. TVR084E An IO error was encountered while performing a VERIFY for file &ddname. TVR085I VSAM reason code from VERIFY = &macrc


TVR086E VSAM file &ddname was already opened. Current OPEN attempt aborted. Explanation Application program issued RVOPEN for a &ddname which is already

open. TVR087E A TESTCB for file &ddname failed to complete successfully. Explanation VSAM TESTCB macro for &ddname was unsuccessful. TVR088E An attempt to issue a #VACBFRE macro has failed. TVR089E A #VACBFRE request was the first VSAM IO call. OPEN must be issued first. TVR090E A #VACBFRE was issued for file &ddname without a preceding #VCLOSE. TVR091E A #VACBFRE was issued for an invalid VFB. Check DDNAME. TVR092E A #VACBFRE failed to find the VFB for DDNAME &ddname. TVR093I File cleanup complete for &ddname. TVR094I Total PUTS for file &ddname = <Puts-number>. TVR095E Access to RRN = 0 is invalid for RRDS file &ddname TVR096E RBA or RRN KEY for file &ddname is too long. Explanation Largest possible RBA is 4,294,967,295. Length of key should be

shorter than 11 bytes. TVR097I Total GETS for file &ddname = <nnnnnn>. TVR098I Total ERASES for file &ddname = <nnnnnn>. TVR099I VSAM file &ddname was temporarily closed. TVR100E An ENDREQ was issued for a an invalid VFB. Check DDNAME. TVR101E An ENDREQ for file &ddname was unsuccessful.


TVR102E An IO error was encountered while performing an ENDREQ for file &ddname. TVR103I VSAM return code from ENDREQ = &macrc TVR104I VSAM reason code from ENDREQ = &macrc TVR105I Total ENDREQ for file &ddname = <nnnnnn> TVR106E The RVGET was issued with MVE mode active. The RPL OPTCD must be set to

LOC. TVR107E An RV... function attempted to use a negative RBA or RRN key value. TVR108E Record length from VSAM catalog is zero for RRDS file &ddname. TVR109I Total POINTS for file &ddname = <nnnnnn> TVR110E An RVPOINT was issued without a KEY parameter. Explanation This is only allowed when the VSAM LRD RPL optcd option

is in effect. TVR111W An RVVERIFY was issued without a preceding RVOPEN. Explanation An implicit RVOPEN will be issued using default ACB

options for file &ddname. TVR112E A #VACB macro for file &ddname has failed during an RVVERIFY. TVR113E A #VOPEN macro for file &ddname has failed during an RVVERIFY. TVR114E A #VCLOSE macro for file &ddname has failed during an RVVERIFY. TVR115 A #VACBFRE macro for file &ddname has failed during an RVVERIFY. TVR116I Total VERIFYS for file &ddname = <nnnnnn>.


TVR117W File &ddname was previously opened unsuccessfully. TVR118E An invalid RVTERM parameter was specified. Please correct. TVR119E An RV... specified an RBA or RRN KEY field that was not numeric. TVR120E A #VGET for file &ddname rejected due to unopened status. TVR121E A #VPOINT for file &ddname rejected due to unopened status. TVR122E A #VPUT for file &ddname rejected due to unopened status. TVR123E A #VCLOSE for file &ddname rejected due to unopened status. TVR124E A #VENDREQ for file &ddname rejected due to unopened status. TVR125E A #VERASE for file &ddname rejected due to unopened status. TVR999I VSAM environment successfully initialized.

REXX/ BDAM Messages 6-1

REXX/BDAM Messages TBR001E BDAM OPEN error for file &&DDEX1 TBR002E Attempt to build DCB for &&DDEX1 has failed TBR003E A BDAM OPEN was issued without a successful preceding #BDCB TBR004E File &&DDEX1 must be allocated prior to making a BDAM request TBR005E Duplicate BFB found for file &&DDEX1 TBR006E MACRF keyword &&DDKWD was not found in DCB keyword table. TBR007E Attempt to build RPL for &&DDEX1 has failed TBR008E An OPEN for file &&DDEX1 returned a nonzero return code TBR009I BDAM file &&DDEX1 was successfully opened TBR010E A TESTCB indicates an OPEN failure for file &&DDEX1 TBR011E An OPEN was issued for an invalid BFB. Check DDNAME TBR012E MACRF keyword &&DDKWD is not permitted in RFA BDAM TBR013W RFA$TBR has not been loaded by RMD function. Assuming VCON access only TBR014E A PUT was issued for an invalid BFB. Check DDNAME TBR015E A PUT request was the first BDAM IO call. OPEN must be issued first TBR016E OPTCD keyword &&DDKWD was not found in RPL keyword table. TBR017E OPTCD keyword &&DDKWD is not permitted in RFA BDAM GET/PUT call


TBR018E Output record size requested is larger than the catalog maximum TBR019E Application requested record size and catalog record size are both zero TBR020E A MODCB macro for file &&DDEX1 failed during PUT processing Check OPTCD for invalid option combinations TBR021E A PUT for file &&DDEX1 was unsuccessful TBR022E An IO error was encountered while performing a PUT for file &&DDEX1 TBR023E A SHOWCB macro was unsuccessful in retrieving control block information following a PUT for file &&DDEX1 TBR024I BDAM return code from RVPUT = &&DDRC1 TBR025E A BDAM CLOSE was issued without a successful preceding #BOPEN TBR026E A CLOSE was issued for an invalid BFB. Check DDNAME TBR027E BDAM CLOSE error for file &&DDEX1 TBR028E A CLOSE for file &&DDEX1 returned a nonzero return code. TBR029I BDAM file &&DDEX1 was successfully closed TBR030E A GET request was the first BDAM IO call. OPEN must be issued first TBR031E A #BGET was issued for an invalid BFB. The specified DDNAME was not found to be in an OPEN status TBR032E Input record size requested is larger than the catalog maximum TBR033E A MODCB macro for file &&DDEX1 failed during GET processing TBR034E A GET for file &&DDEX1 was unsuccessful TBR035E An IO error was encountered while performing a GET for file &&DDEX1 TBR036E A SHOWCB macro was unsuccessful in retrieving control block information following a GET for file &&DDEX1 TBR037I BDAM return code from RVGET = &&DDRC1 TBR038E Detected an attempt to GET a record after an end of file indication was already presented for file &&DDEX1 TBR039E End of file encountered for file &&DDEX1 TBR040E MODCB failure for file &&DDEX1 in #BDCB routine


TBR041E A REXX &&DDFUNC function has completed unsuccessfully TBR042E An attempt to issue a #BDCB macro has failed. TBR043E A #BOPEN macro failed processing file &&DDEX1 TBR044I A #BOPEN was successful for file &&DDEX1 TBR045E A #BCLOSE macro failed processing file &&DDEX1 TBR046I A #BCLOSE was successful for file &&DDEX1 TBR047E No IOAREA was specified in a &&DDFUNC VSAM call TBR048E Invalid &&DDFUNC parameter specification TBR049E Unsuccessful &&DDFUNC macro call TBR050I File &&DDEX1 completed without explicitly specifying OPTCD TBR051I A VPUT request has specified an OPTCD override TBR052I A VGET request has specified an OPTCD override TBR053I A VPOINT request has specified an OPTCD override TBR054I A #BGET for file &&DDEX1 is making use of default RPL OPTCD options TBR055I A #BPUT for file &&DDEX1 is making use of default RPL OPTCD options TBR056I BDAM reason code from RVPUT = &&DDRC1 TBR057I BDAM reason code from RVGET = &&DDRC1 TBR058I BDAM return code from OPEN = &&DDRC1 TBR059I BDAM reason code from OPEN = &&DDRC1 TBR060I BDAM return code from CLOSE = &&DDRC1 TBR061I BDAM reason code from CLOSE = &&DDRC1 TBR062E A GET was issued with MVE mode active but no IOAREA defined TBR063W A LOC mode GET was issued. IOAREA will be ignored TBR064I A #BPOINT for file &&DDEX1 is making use of default RPL OPTCD options TBR065E A MODCB macro for file &&DDEX1 failed during POINT processing TBR066E A POINT for file &&DDEX1 was unsuccessful TBR067I BDAM return code from POINT = &&DDRC1


TBR068I BDAM reason code from POINT = &&DDRC1 TBR069E An ERASE was issued for an invalid BFB. Check DDNAME. TBR070E A POINT was issued for an invalid BFB. Check DDNAME. TBR071I BDAM return code from ERASE = &&DDRC1 TBR072I BDAM reason code from ERASE = &&DDRC1 TBR073E An ERASE for file &&DDEX1 was unsuccessful TBR074E An I/O error was encountered while performing an ERASE for file &&DDEX1 TBR075E Unknown BDAM file type detected. Notify RAI. TBR076E Unknown BDAM file type returned from TESTCB. Notify RAI TBR077W RPL OPTCD of MVE has been overlaid with LOC. RVGET continuing TBR078E Unable to override MVE OPTCD. Check RVGET option string TBR079E A VERIFY was issued for an invalid BFB. Check DDNAME. TBR080E A MODCB macro for file &&DDEX1 failed during VERIFY processing TBR081E A VERIFY for file &&DDEX1 was unsuccessful TBR082I BDAM return code from VERIFY = &&DDRC1 TBR083E An IO error was encountered while performing a POINT for file &&DDEX1 TBR084E An IO error was encountered while performing a VERIFY for file &&DDEX1 TBR085I BDAM reason code from VERIFY = &&DDRC1 TBR086E BDAM file &&DDEX1 was already opened. Current OPEN attempt aborted TBR087E A TESTCB for file &&DDEX1 failed to complete successfully TBR088E An attempt to issue a #BDCBFRE macro has failed TBR089E A #BDCBFRE request was the first BDAM IO call. OPEN must be issued first TBR090E A #BDCBFRE was issued for file &&DDEX1 without a preceding #BCLOSE TBR091E A #BDCBFRE was issued for an invalid BFB. Check DDNAME TBR092E A #BDCBFRE failed to find the BFB for DDNAME &&DDEX1 TBR093I File cleanup complete for &&DDEX1 TBR094I Total PUTS for file &&DDEX1 = &&DDCT1


TBR095E Access to RRN = 0 is invalid for RRDS file &&DDEX1 TBR096E RBA or RRN KEY for file &&DDEX1 is too long. Largest possible RBA is 4,294,967,295. Key should be shorter than 11 bytes TBR097I Total GETS for file &&DDEX1 = &&DDCT1 TBR098I Total ERASES for file &&DDEX1 = &&DDCT1 TBR099I BDAM file &&DDEX1 was temporarily closed TBR100E An ENDREQ was issued for an invalid BFB. Check DDNAME TBR101E An ENDREQ for file &&DDEX1 was unsuccessful TBR102E An IO error was encountered while performing an ENDREQ for file &&DDEX1 TBR103I BDAM return code from ENDREQ = &&DDRC1 TBR104I BDAM reason code from ENDREQ = &&DDRC1 TBR105I Total ENDREQ for file &&DDEX1 = &&DDCT1 TBR106E The RVGET was issued with MVE mode active. The RPL OPTCD must be set to LOC TBR107E An &&DDFUNC function attempted to use a negative RBA or RRN key value TBR108E Record length from BDAM catalog is zero for RRDS file &&DDEX1 TBR109I Total POINTS for file &&DDEX1 = &&DDCT1 TBR110E An RVPOINT was issued without a KEY parameter. This is only allowed when the BDAM LRD RPL optcd option is in effect TBR111W An RVVERIFY was issued without a preceding RVOPEN. An implicit RVOPEN will be issued using default DCB options for file &&DDEX1 TBR112E A #BDCB macro for file &&DDEX1 has failed during an RVVERIFY TBR113E A #BOPEN macro for file &&DDEX1 has failed during an RVVERIFY TBR114E A #BCLOSE macro for file &&DDEX1 has failed during an RVVERIFY TBR115E A #BDCBFRE macro for file &&DDEX1 has failed during an RVVERIFY TBR116I Total VERIFYs for file &&DDEX1 = &&DDCT1 TBR117W File &&DDEX1 was previously opened unsuccessfully TBR118E An invalid RVTERM parameter was specified. Please correct TBR119E An &&DDFUNC specified an RBA or RRN KEY field that was not numeric


TBR120E A #BGET for file &&DDEX1 rejected due to unopened status TBR121E A #BPOINT for file &&DDEX1 rejected due to unopened status TBR122E A #BPUT for file &&DDEX1 rejected due to unopened status TBR123E A #BCLOSE for file &&DDEX1 rejected due to unopened status TBR124E A #BENDREQ for file &&DDEX1 rejected due to unopened status TBR125E A #BERASE for file &&DDEX1 rejected due to unopened status TBR126E Attempt to purge TCB slot failed TBR127E An error was encountered trying to establish RECOVERY environment TBR128E An error was encountered trying to terminate RECOVERY environment TBR129I A &&ABENDCDE ABEND has occurred. RECOVERY processing complete TBR130I ABEND bypassed. Will schedule RETRY TBR131E RETRY attempt will be bypassed. ABEND in progress TBR132I Smart/MONITOR RETRY in progress TBR990E ATTEMPT TO CLOSE MSG FILE HAS FAILED TBR991E FAILURE INITIALIZING MESSAGE LOG TBR992E ERROR ISSUING REXX EXCOM MACRO TBR993E INVALID RVMSG LEVEL PARAMETER TBR994E INVALID RVMSG ROUTE PARAMETER TBR995E PMVBREXX FUNCTION HAS FAILED TBR996E VCT NOT LOADED BY RFA #RMD TBR997E FAILURE INITIALIZING REXX BDAM ENVIRONMENT TBR998E MESSAGE SERVICE ERROR IN PMVBXXX TBR999I BDAM environment successfully initialized

Reusable Function Architecture (RFA) Messages 7-1

Reusable Function Architecture (RFA) Messages

Reusable Function Architecture (RFA) is a set of software core functions used by many RAI products. Messages presented here are mostly packaged as ISPF messages in the RLXMLIB library. Messages presented without explanation are self evident, and associated with the field currently pointed to by the cursor on the ISPF panel.

Data Conversion Messages These messages are associated with panel fields containing values to be edited with a specific format. When you enter an incorrect value, one of these messages will be displayed.

PFK990 INTEGER variable value invalid PFK991 SMALLINT variable value invalid PFK992 DEC150 variable value invalid PFK993 DEC55 variable value invalid PFK994 CHAR5 variable value invalid PFK995 VARCHAR10 variable value invalid PFK996 INDICATOR variable value invalid PFK997 INTEGER variable value invalid PFK998 INTEGER variable value invalid


MVS Messages

PMV000 Allocation error. r15 = &RC, error code = &EC, reason code = &IC Explanation Dynamic allocation system service (SVC 99) was issue and failed. Action See Interpreting DYNALLOC return codes in the current version of IBM

publication z/OS VxRy MVS Authorized Assembler Services Guide for explanation of DYNALLOC services return and reason codes.

PMV001 &USER lacks authority to access &DSN Explanation UserID &USER does not have RACF authority to access a dataset &DSN. Action Review system log for RACF messages. Authorize user access to &DSN is

required. PMV002 Abend &CODE Reason &REASON occurred during open processing PMV003 File is not open after return from Open SVC PMV004 CAMLST/LOCATE system service failed to retrieve DS volume serial # PMV005 Dataset not cataloged PMV006 Failed to acquire a buffer for the open file PMV007 CAMLST/OBTAIN system service failed to retrieve dataset label PMV009 Try LISTA STatus command PMV011 Invalid project - Reenter Project name PMV012 Invalid library - Reenter library name PMV013 Enter Type Qualifier PMV014 Enter closing parenthesis after member name PMV015 Member name must be between 1 and 8 characters long PMV016 No System Diagnostic Work Area available PMV017 Abend profile formatted from MVS System Diagnostic Work Area


Messages associated with generic OS/MVS routines PMV050 Link to module &PMVMOD failed. Abend = &PMVAC Reason = &PMVARC PMV051 Attach of module &PMVMOD failed. Abend = &PMVAC Reason = &PMVARC PMV052 Load of module &PMVMOD failed. Abend = &PMVAC Reason = &PMVARC PMV053 A severe error occurred in attempting to invoke exec &PMVEXEC PMV054 Recursive abend detected - PMVRTM1 will NOT attempt retry Numeric Input Conversion Messages

PSR010 Invalid character(s) present in edited numeric input field PSR011 More than 1 plus + or minus - sign present in field PSR012 Invalid blank or numeric editing character embedded in field PSR013 Internal numeric value truncated during conversion PSR014 More digits to left of decimal point than allowed for SQL column PSR015 Scale value truncated during conversion PSR016 Smallint value does not fall within +32767 and -32768 range PSR017 Integer value outside +2147483648 and -2147483648 range PSR018 Only plus + or minus - sign present in field PSR020 Significance or underflow exception converting to floating point PSR021 Overflow - Valid floating point range is from -7.2E+75 to +7.2E+75 PSR022 Floating value does not fall within 7.2E+75 and -5.4E-79 range PSR023 Invalid characters present in floating point char string PSR024 Severe / unexpected error in char -> float conversion routine


Date conversion routine messages

PSR030 Month or days component of a date has non numeric digits PSR031 ISO date (YYYY-MM-DD) has fewer than 8 characters PSR032 Expected dash - between ISO/JIS date components PSR033 Invalid characters present in date field PSR034 Month must be in range 1 - 12 PSR035 Day portion of date cannot be zero PSR036 Day value is too high for the corresponding month PSR037 Expected slash between USA formatted date components PSR038 Invalid output date format option PSR039 Expected period between EUR formatted date components Time conversion routine messages

PSR040 Time string has fewer than 4 characters PSR041 Invalid format option for time data type PSR042 Invalid delimiter character between time string components PSR043 USA time format requires : between Hours and Minutes as in 12:23 PSR044 USA time format requires space before AM or PM PSR045 USA time format requires an AM or PM designation PSR046 USA time format does not allow 00 for hour value except 00:00 PSR047 Invalid characters present in time string PSR048 Time string HOURS value not within the range 0 – 24 PSR049 Time string MINUTES or SECONDS value not in the range 0 - 60 Time and timestamp conversion routine messages


PSR050 USA Hours value must be in the range 1 thru 12 (except 00:00) PSR051 Invalid format option for a column whose data type is TIME PSR052 Timestamp string must be at least 16 characters in length PSR053 Expected dash between YYYY-MM-DD-HH timestamp components not found PSR054 Microsecond specification must consist of numeric digits PSR055 Expected a period between hh.mm.ss.nnnnnn timestamp components PSR056 A maximum of 6 numeric digits may be specfied for micro seconds

Miscellaneous Messages for PSR common routines

PSR060 Command requires parameter(s) PSR061 Command is not recognized

Reusable Function Architecture Messages

RFA000 Trace process unable to match issuing macro name &MACRO


AcceleREXX Messages 8-1

AcceleREXX Messages

AcceleREXX Compile Messages RCX020 Select EXEC(s) to be compiled and linked into a composite load module RCX021 Specify AcceleREXX compile and Link Edit options and press ENTER RCX022 Select previously compiled REXX EXECs for Link Edit in

&RCXLMOD RCX023 Respecify AcceleREXX compile and Link Edit options RCX024 Select EXEC(s) to be compiled and linked into discrete load modules

AcceleREXX Dialog Messages RCX030 Names of AcceleRexx product and user libraries were created RCX031 Library names were reviewed / adjusted RCX032 Job card parameters were saved RCX033 Screen colors where reviewed / adjusted RCX401E Invalid or uncataloged data set &DSNIN


RCX402E Either CSECT or MEMBER must be specified RCX403E Invalid REXX EXEC input data set name = &RCXIDSN RCX404E REXX EXEC source is not PDS use other DSN field RCX405E Failed to open input file, rc= &RC RCX406E Failed to list input file, rc= &LMRC RCX407E Member not found / no members in input REXX EXEC data set RCX408E No selection was made from the member list RCX409E Input REXX EXEC dataset / member not exist RCX410E Failure to create card table - more than one AcceleREXX active RCX411E Failure detected in RAIPWD dialog RC=&RC RCX412I Specify / Verify AcceleREXX installation parameters and press

ENTER RCX413I AcceleREXX installation parameters successfully updated RCX420 AcceleREXX IVP jobstream being tailored - please wait RCX421 AcceleREXX compile jobstream being tailored - please wait

Relational Architects Common Messages 9-1

Relational Architects Common Messages

RAI Product Password Verification Messages These messages are issued when a RLX product is invoked without proper authorization. You should obtain product access keys from RAI technical support by issuing an administrative request using the RAI web site: http://www.relarc.com/form/administrative_request, or by calling technical support at +1.201.420.0400.

RAI001E Load of &module failed. Abend = &abend Reason = &reason Explanation: The RAI password authorization module whose name is represented by

&module name in the prototype text could not be loaded. The abend code (represented by &abend in the prototype text) and abend reason code (represented by &reason in the prototype text) further describe the error. If the abend code is 806, then the RAI password load module &module could not be found.

Developer Response: Check with the RAI product administrator to ensure a password load

module was created during installation. If it was created, ensure the load module is in a library accessible to the program fetch search order. Options include: Add a STEPLIB DD statement to the failing jobstep or JOBLIB DD statement to the failing jobstream. The load module library defined by either the STEPLIB or JOBLIB file must contain the password authorization module. A third option is to include the password load module library in the MVS linklist concatenation. The job should then be rerun.

Operator Response: Same as developer response. System Programmer Response: None required Problem Determination: Collect SYSUDUMP.

http://www.relarc.com/form/administrative_request�


RAI002E Specify product passwords before operating &product Explanation: An attempt was made to utilize an RAI program product &product

before it was fully installed. The RAI product administrator should be notified and advised that a pair of product passwords have to be specified BEFORE any RAI software product will operate correctly.

Developer Response: None required Operator Response: None required System Programmer Response: Generate a password load module via the RAI password definition

dialog. Make the load module and library accessible to MVS program fetch.

Problem Determination: None required RAI003E &product product usage has expired on CPU &cpu - contact vendor Explanation: The RAI program product whose name is represented by &product in

the prototype text will no longer operate on the CPU whose serial number is represented by &cpu (e.g. 1234) in the prototype text. This is because the term of usage has elapsed. This could be due to the fact that the RAI program product &product was in for a trial or was licensed on a term rather than a perpetual basis. In order to continue to use the product, contact the vendor and obtain new passwords.

Developer Response: None required Operator Response: None required System Programmer Response: None required Problem Determination: None RAI004W &product product usage has &days days remaining - Contact vendor Explanation: This warning message indicates that the RAI product whose name is

represented by &product in the prototype text will cease to operate in &days days. RAI should be contacted to arrange to extend the use of the product. Otherwise, it will cease to function in NN days.

Developer Response: None required Operator Response: None required System Programmer Response: None required Problem Determination: None


RAI005E &product Version &version not authorized on CPU &cpu Explanation: The set of passwords supplied by RAI for the product represented by

&product in the prototype text do not authorize the use of the version and release of the product represented by &version in the prototype text. RAI should be contacted to obtain a pair of passwords consistent with the currently installed version and release of the product.

Developer Response: None required Operator Response: None required System Programmer Response: None required Problem Determination: Collect a SYSUDUMP. Add a DSNTRACE DD statement RAI006E CPU serial &cpu not authorized to run &product Explanation: The RAI product whose name is represented by &product in the

prototype text is authorized to run on the processor complex whose CPU serial number is represented by &cpu in the prototype text. The RAI product administrator should add a pair of password entries for this CPU serial number to the RAI password verification load module tailored for product &product. If RAI did not furnish these passwords, then the vendor should be contacted to obtain a pair of passwords which will enable the currently installed version and release of product &product to operate on CPU serial number &cpu.

Developer Response: None required Operator Response: None required System Programmer Response: None required Problem Determination: None


RAI Product Administration Messages These messages are issued when you are conducting an ISPF- based Password Definition Dialog. For customers using the RAI Server Address Space, passwords are installed in the RAI Server without utilization of this dialog.

RAI010 Specify temporary password for &RAIPROD trial RAI011 Press Enter to tailor CPU/Password table or END/RETURN to exit dialog RAI012 CPU/Password table being tailored - please wait RAI013 Specify 1 - Edit jobstream, 2 - Submit job, or END/RETURN to bypass RAI014 Jobstream being tailored - please wait RAI015 Press Enter to tailor Assemble/Link Edit job or END/RETURN to bypass RAI016 Specify new &RAIPROD Password values and press ENTER RAI017 Review and change &RAIPROD Password values and press ENTER RAI018 Press ENTER to delete &PROD Password or END/RETURN to bypass RAI019 Browse &PROD Password values. Then press ENTER to continue RAI020 Specify A - Add, C - Change, D - Delete, or B - Browse RAI021 New &PROD Password added successfully RAI022 &PROD Password changed successfully RAI023 &RAIPROD Password deleted successfully RAI024 Duplicate &RAIPROD serial number - add failed RAI025 CPU serial number may not be changed - Instead DELETE, then ADD RAI026 Temp passwords upgraded to permanent passwords for a specific CPU RAI130 Specify &RAIPROD Installation Parameters and press ENTER RAI131 &RAIPROD Installation Parameters updated successfully RAI132 Verify &RAIPROD library dataset names and press ENTER RAI133 Specify IBM system load libraries and press ENTER RAI134 Specify &RAIPROD Job and Jobparm values and press ENTER RAI135 Specify 1 - Edit tailored jobstream or 2 - Immediately submit job


RAI140 No RLX product passwords defined - Contact RLX adminstrator or Vendor

Member List Dialog (MLD) Messages

RAI150E Invalid or uncataloged data set &raidsn RAI151E &raidsn is an invalid data set name RAI153E &ZERRLM RAI154E Input dataset is not a PDS: Use the other DSN field RAI155E Failed to open input file, rc= &RC RAI156E Failed to list input file, rc= &LMRC RAI157E Member not found / no members in input data set RAI158I No library members selected for processing RAI159E Input dataset or member does not exist RAI160 &mslcount member(s) selected for processing RAI161 Output dataset is not partitioned RAI162E Severe error referencing output dataset RAI163E Invalid or uncataloged data set/member &mslidsn RAI164E Member &mslmbr not found RAI172E Either CSECT or MEMBER must be specified RAI173E Invalid REXX EXEC input data set name = &RAIIDSN RAI174E REXX EXEC source is not PDS use other DSN field RAI175E Failed to open input file, rc= &RC RAI176E Failed to list input file, rc= &LMRC RAI177E Member not found / no members in input REXX EXEC data set RAI178E No selection was made from the member list RAI179E Input REXX EXEC dataset or member does not exist RAI180 Dataset not catalogued. Please respecify RAI181 Library member not found. Please respecify


RAI182 Severe error returned by LISTD command. Return code = &rc RAI183 Primary command not recognized - Valid commands are L, LOC and LOCATE RAI184 Invalid row command: only S=Select or U=Unselect are allowed RAI185 Member already selected RAI186 Member was not selected -- nothing to Unselect

User SVC dialog Messages Since the introduction of the RAI Server Address Space, Product User SVC is no longer utilized. Instead, the more secure, proprietary APF authorization mechanism is used.

RAI196 Specify LPA update parms and press ENTER or press END/RETURN to exit RAI197 the LPALIB update jobstream is being tailored - Please Wait RAI198 Press Enter to build MVS update jobstream or END/RETURN to bypass RAI199 ESR or SVC code must be a numeric value between 200 and 255


Abend Detection Messages RAI901I SYSUDUMP file detected - Dump will be requested Explanation: The Relational Architects common abend handler (module

PMVRTM1) detected a file named SYSUDUMP that is allocated to the jobstep. The abend handler will therefore request that a dump be written to the SYSUDUMP dataset.

Developer Response: Analyze the dump and any error messages to determine why the application terminated abnormally.

Operator Response: Notify site’s technical support staff or the application developer Problem Determination: Analyze the dump, JES logs and any application error messages to

determine why the application terminated abnormally. RAI997E Recursive abend detected. - PMVRTM1 will not attempt retry Explanation: The Relational Architects common abend handler (module

PMVRTM1) detected a recursive abend. The RAI abend handler therefore lets abnormal termination to proceed (percolate).

Developer Response: Analyze the dump and any error messages to determine why the application terminated abnormally.

Operator Response: Notify site’s technical support staff or the application developer Problem Determination: Analyze the dump, JES logs and any application error messages to

determine why the application terminated abnormally. RAI998E Abend XXXXXX detected in subtask XXXX Reason = xxxxxxxx Explanation: The Relational Architects common abend handler (module

PMVRTM1) detected the abnormal completion of a task. XXXX denotes the task completion code which is either a User abend denoted by the letter U and four decimal digits (for example U 2001) or a system abend denoted by the letter S and three hexadecimal digits (for example S E37).

Subtask xxxx denotes the symbolic name by which the RAI task and

process is known internally. This name is meaningful to RAI support staff. Reason xxxxxxxx denotes the reason code (comprised of 8 hexadecimal digits) which is associated with the abend.

Developer Response: Analyze any error messages and a dump if available to determine why

the application terminated abnormally. Operator Response: Notify site’s technical support staff or the application developer Problem Determination: Analyze the dump, JES logs and any application error messages to

determine why the application terminated abnormally.


Documents

Relational Arc - ftpdocs.broadcom.com