GASP -13 DISC LOCKED THE CARTRIDGE SPECIFIED IS LOCKED. INITIALIZE THE CARTRIDGE IF IT WAS NOT INITIALIZED, OTHERWISE KEEP TRYING. "" GASP -12 EOF OR SOF ERROR AN ATTEMPT WAS MADE TO READ, WRITE, OR POSITION A FILE BEYOND THE FILE BOUNDARIES. CHECK THE RECORD POSITION PARAMETERS. THE RESULTS DEPEND ON THE FILE TYPE AND THE CALL. "" GASP -8 FILE OPEN OR LOCK REJECTED AN ATTMPT WAS MADE TO OPEN A FILE THAT WAS ALREADY OPENED EXCLUSIVELY OR WAS ALREADY OPENED TO EIGHT PROGRAMS, OR THE CARTRIDGE CONTAINING THE FILE IS LOCKED. USE THE CL OR DL COMMAND TO LOCATE THE LOCK. IF THE FILE IS BEING PACKED, CHECK TO SEE IF SPOOLING IS SHUT DOWN. "" GASP -7 ILLEGAL SECURITY CODE OR ILLEGAL WRITE ON LU2 OR 3 1. AN ATTEMPT WAS MADE TO ACCESS A FILE WITHOUT SPECIFYING THE SECURITY CODE OR WITH THE WRONG SECURITY CODE. FIND OUT THE CORRECT CODE AND USE IT OR DO NOT ACCESS THE FILE. OR 2. AN ATTEMPT WAS MADE BY A SESSION USER (NOT THE SYSTEM MANAGER) TO WRITE ON LU 2 OR 3. SESSION USERS DO NOT HAVE WRITE ACCESS TO LU 2 OR 3. "" GASP -6 FILE NOT FOUND AN ATTEMPT WAS MADE TO ACCESS A FILE THAT CANNOT BE FOUND. CHECK THE FILE NAME. "" GASP -4 MORE THAN 32767 RECORDS IN A TYPE 2 FILE AN ATTEMPT WAS MADE TO CREATE A TYPE 2 FILE WITH TOO MANY RECORDS OR WITH A RECORD SIZE THAT IS TOO LARGE. CHECK THE SIZE PARAMETER. "" GASP -2 DUPLICATE FILE NAME A FILE ALREADY EXISTS WITH THE NAME SPECIFIED. REPEAT THE COMMAND WITH A NEW NAME OR PURGE THE EXISTING FILE. "" GASP -1 DISC ERROR THE DISC IS DOWN. TRY AGAIN AND THEN REPORT THE PROBLEM TO THE SYSTEM MANAGER. "" GASP 1 DISC ERROR NN DISC ASSOCIATED WITH LU NN IS DOWN; REPORT PROBLEM TO THE SYSTEM MANAGER. "" GASP 2 NUMBER OUT OF RANGE NUMBER ENTERED IN GASP INITIALIZATION IS INCONSISTENT WITH PREVIOUS ENTRIES OR EXCEEDS MAXIMUM SPECIFIED AT GENERATION; CHECK LAST ENTRY AND CHANGE. "" GASP 3 BAD JOB NUMBER! SPECIFIED JOB NUMBER NOT CURRENTLY ASSIGNED; CHECK ASSIGNED JOB NUMBERS WITH DJ COMMAND; RE-ENTER COMMAND WITH VALID JOB NUMBER. "" GASP 4 ILLEGAL STATUS COMMAND IS NOT VALID FOR CURRENT STATE OF JOB OR SPOOL FILE; CHECK STATUS WITH DJ OR DS. "" GASP 5 ILLEGAL COMMAND COMMAND NOT RECOGNIZED BY GASP; CHECK AND RE-ENTER COMMAND CORRECTLY. "" GASP 6 NOT FOUND SPECIFIED JOB OR SPOOL NOT CURRENTLY ASSIGNED; CHECK WITH DJ OR DS. "" GASP 43 LU NOT FOUND IN SST THE OUTSPOOL LU SPECIFIED IN COMMAND IS NOT DEFINED IN THE SESSION SWITCH TABLE FOR THIS SESSION USER. USE FMGR SL COMMAND TO ADD THE LU TO THE SST OR USE ANOTHER OUTSPOOL LU. "" GASP 46 INSUFFICIENT CAPABILITY AN ATTEMPT WAS MADE TO EXECUTE A COMMAND THAT REQUIRES A HIGHER CAPABILITY LEVEL THAN THE CAPABILITY LEVEL DEFINED FOR THIS SESSION USER. "" GASP 55 MISSING PARAMETER A REQUIRED PARAMETER HAS BEEN OMITTED. CHECK THE COMMAND AND RE-ENTER IT WITH THE MISSING PARAMETER. "" GASP 56 BAD PARAMETER A PARAMETER WAS SPECIFIED INCORRECTLY; CHECK THE COMMAND AND RE-ENTER IT CORRECTLY. "" LGON 06 THIS IS AN INFORMATIONAL DIAGNOSTIC. THE STATION (TERMINAL) BEING LOGGED ONTO HAS A CONFIGURATION TABLE ENTRY WHICH IS A DUPLICATE OF AN ENTRY IN THE USERS ACCOUNT FILE ENTRY. IF THE USER HAS THE CAPABILITY TO MAKE CHANGES IN THE SESSION SWITCH TABLE (SL,X,Y), BOTH THE CONFIGURATION TABLE AND THE USERS ACCOUNT FILE DEFINITION (OF THE SESSION LU) ARE REPORTED. IN EITHER CASE, THE USER'S ACCOUNT FILE DEFINITION IS USED. CONTACT YOUR SYSTEM MANAGER TO HAVE THE CONFLICT REMOVED. "" LGON 09 YOUR SESSION HAS EXCEEDED THE MAXIMUM SESSION SWITCH TABLE SIZE. THE OVERFLOW WAS DETECTED IN ONE OF THE FOLLOWING AREAS: BUILDING THE SST ENTRIES DEFINED BY THE USER'S ACCOUNT ENTRY, BUILDING SST ENTRIES DEFINED BY THE STATION CONFIGURATION TABLE OR MOUNTING SYSTEM GLOBAL DISCS. CONTACT YOUR SYSTEM MANAGER AS YOU MAY BE MISSING SOME DEVICE DEFINITIONS. "" LGON 11 THE LOGON PROGRAM RECEIVED THE SPECIFIED ERROR WHEN ATTEMPTING TO MOUNT A PRIVATE OR GROUP DISC TO THIS SESSION. CHECK THE TERMINAL USERS MANUAL (ERROR SUMMARY) FOR MORE INFORMATION. "" LGON 13 THIS IS AN INFORMATIONAL DIAGNOSTIC. LOGON DETECTED A USER SST WHICH ATTEMPTED TO REDEFINE A SYSTEM DISC'S LOGICAL UNIT NUMBER. DISC LU'S MUST BE DIRECT MAPS (SESSION LU=SYSTEM LU). CONTACT YOUR SYSTEM MAN- AGER TO CORRECT YOUR ACCOUNT. "" ACCT 012 LU NOT IN SESSION SWITCH TABLE ENTER THE CORRECT LU OR EXIT ACCTS AND PUT LU IN SST WITH SL COMMAND "" ACCT 004 ILLEGAL LU A LU WAS SPECIFIED WHICH: 1) CAN NOT HANDLE BINARY DATA 2) IS NOT AN INPUT DEVICE 3) IS NOT AN OUTPUT DEVICE 4) THE DEVICE IS WRITE PROTECTED "" ACCT 013 TRANSFER STACK OVERFLOW THE TRANSFER STACK IS ONLY 10 DEEP TR,-11 CLEARS THE TRANSFER STACK "" ACCT 046 INSUFFICIENT CAPABILITY AN ATTEMPT WAS MADE TO EXECUTE A COMMAND WHICH IS RESERVED FOR GROUP MANAGERS OR THE SYSTEM MANAGER. "" ACCT-200 ACCOUNT NOT FOUND GROUP ACCOUNT MUST BE DEFINED BEFORE A USER CAN BE ASSIGNED TO IT "" ACCT-201 NO FREE ACCOUNTS THE "LO,0" COMMAND CAN BE USED TO EXPAND THE ACCOUNTS FILE "" ACCT-202 ACCOUNT WITH THIS NAME ALREADY EXISTS "" ACCT-203 INVALID ACCOUNT NAME 1) ONLY 10 ALPHANUMERIC CHARACTERS ARE ALLOWED FOR A NAME. 2) WHEN LINKING TO AN ACCOUNT WHICH BELONGS TO GROUP GENERAL ".GENERAL" MUST BE SPECIFIED. "" ACCT-204 INVALID PASSWORD 1) THE PASSWORD OF THE SYSTEM MANAGER IS REQUIRED TO RUN ACCTS FROM A NON SESSION CONSOLE. 2) THE PASSWORD OF THE ACCOUNT TO WHICH THIS IS BEING LINKED IS REQUIRED. 3) THE PASSWORD FOR CURRENT ACCOUNT IS INCORRECT. 4) THE NEW PASSWORD CONTAINS AN ILLEGAL CHARACTER. THE CHARACTER MUST BE PRINTABLE AND NOT A DELIMITER ( . , * / ). "" ACCT-205 INVALID COMMAND ENTER "HE" TO GET THE COMMANDS "" ACCT-206 INVALID FILE NAME "" ACCT-207 INVALID CAPABILITY CAPABILITY MUST BE BETWEEN 1 AND 63 "" ACCT-208 INVALID DISC LIMIT ONLY 60 DISCS ARE ALLOWED "" ACCT-209 INVALID SST ENTRY SESSION LU MUST BE GREATER THAN 3 AND LESS THAN 64 SYSTEM LU MUST BE GREATER THAN 0 AND LESS THAN 255 SESSION LU IS ALREADY DEFINED. "" ACCT-210 CONFLICT IN SST DEFINITION USER AND GROUP SST'S DISAGREE "" ACCT-211 USER OR GROUP ID NOT AVAILABLE ENTER "LIST,USER,@.@,6,ID" TO FIND LARGEST GROUP ID AND SMALLEST USER ID PURGE AND REBUILD THE CONFLICTING ACCOUNT(S) "" ACCT-212 INVALID NUMBER OF SST SPARES MUST BE BETWEEN 0 AND 60 SPARES PLUS DISC LIMIT MUST BE LESS THAN 68 "" ACCT-213 INVALID MEMORY REQUEST MEMORY REQUEST MUST BE BETWEEN 70 AND 7000 WORDS "" ACCT-215 LIST NAMR IN TRANSFER STACK REISSUE TR COMMAND "" ACCT-218 SESSION NOT SHUT DOWN SESSION MUST SHUT DOWN FOR LOAD, "" ACCT-219 NOT ENOUGH ROOM IN FILE FOR NEW TABLE ENTER "LO,0" TO EXPAND FILE "" ACCT-220 CORRUPT STATION TABLE SPARES SORRY MUST BUILD ACCOUNTS FILE FROM SCRATCH "" ACCT-221 NOT AN ACTIVE SESSION THE SESSION ADDRESSED IS NOT ACTIVE "" ACCT-222 ILLEGAL SYSTEM LU SYSTEM LU MUST BE BETWEEN 1 AND 255 "" ACCT-223 ILLEGAL SHUT DOWN PARAMETER SHUT DOWN OPTIONS ARE: 1)"SD" SHUT DOWN THE SESSION SYSTEM 2)"SD,RE SHUT DOWN THE SESSION SYSTEM AND RELEASE SESSION MEMORY 3)"SD,,RP" SHUT DOWN SESSION AND RELEASE PRIVATE DISCS 4)"SD,,RG" SHUT DOWN SESSION AND RELEASE GROUP DISCS CANNOT BE TERMINAL LU FROM WHICH ACCTS IS RUNNING. YOU CANNOT SHUT DOWN YOUR OWN SESSION. "" ACCT-225 SESSION MEMORY CAN NOT BE RETURNED TO SYSTEM (REBOOT) "" ACCT-046 GREATER THAN 255 EXTENTS ATTEMPT TO CREATE EXTENT 256. MAKE FILE SIZE OF MAIN LARGER. "" ACCT-099 DIRECTORY MANAGER EXEC REQUEST WAS ABORTED AN EXEC REQUEST MADE BY D.RTR WAS ABORTED. MAKE SURE THAT ALL DISCS BEING ACCESSED ARE UP. NOTIFY SYSTEM MANAGER. "" ACCT-041 NO ROOM IN SST "" ACCT-040 LU NOT FOUND IN SST TRYING TO ACCESS AN LU THAT IS NOT IN YOUR SST. USE THE SL COMMAND TO ADD THE LU TO THE SST. "" ACCT-039 CONFLICT IN SST DEFINITION "" ACCT-035 ALREADY 63 DISCS MOUNTED TO SYSTEM AN ATTEMPT WAS MADE TO MOUNT A DISC WHEN THERE ARE ALREADY 63 DISCS MOUNTED. A DISC WILL HAVE TO BE DISMOUNTED BEFORE A NEW ONE MAY BE MOUNTED. "" ACCT-034 DISC ALREADY MOUNTED. AN ATTEMPT WAS MADE TO MOUNT A DISC THAT IS ALREADY MOUNTED ON THE CARTRIDGE LIST. EITHER DISMOUNT THE DUPLICATE DISC OR MOUNT A DIFFERENT ONE. "" ACCT-033 NOT ENOUGH ROOM ON CARTRIDGE AN ATTEMPT WAS MADE TO ACCESS A CARTRIDGE WHICH HAS NO MORE ROOM. TRY USING ANOTHER CARTRIDGE OR DECREASE THE FILE SIZE. "" ACCT-032 CARTRIDGE NOT FOUND AN ATTEMPT WAS MADE TO ACCESS A CARTRIDGE THAT CANNOT BE FOUND IN THE CARTRIDGE LIST. CHECK THE CARTRIDGE NUMBER FOR CORRECTNESS. "" ACCT-030 VALUE TOO LARGE FOR PARAMETER "" ACCT-026 QUEUE FULL OR MAX PENDING SPOOLS EXCEEDED THE SPOOL QUEUE IS FULL OR THE MAXIMUM NUMBER OF PENDING SPOOLS HAS BEEN EXCEEDED. THE JOB MUST BE RE-RUN WHEN THE SPACE BECOMES AVAILABLE. "" ACCT-025 NO SPLCON ROOM THE SPLCON IS FULL. THIS ERROR MAY OCCUR WHEN THE SPOOL SYSTEM IS COMPETING WITH PROGRAMS USING THEIR OWN SPOOLING FILE AND RUNNING OUTSIDE OF BATCH. "" ACCT-024 NO MORE BATCH SWITCHES THE LU SWITCH TABLE IS FULL. THE SIZE OF THE SWITCH TABLE SPECIFIED AT SYSTEM GENERATION IS INADEQUATE. NOTIFY THE SYSTEM MANAGER OF THIS CONDITION. "" ACCT-023 NO AVAILABLE SPOOL FILES ALL SPOOL FILES ARE CURRENTLY BEING USED. RE-RUN THE JOB AFTER A SPOOL FILE BECOMES AVAILABLE. "" ACCT-022 NO AVAILABLE SPOOL LU'S ALL SPOOL LOGICAL UNITS ARE CURRENTLY UNAVAILABLE. RE-RUN THE JOB AFTER A SPOOL LU BECOMES AVAILABLE. "" ACCT-021 ILLEGAL DESTINATION LU THE LU SPECIFIED WAS NOT ALLOCATED BY GASP. TRY AGAIN USING A LU ALLOCATED BY GASP. "" ACCT-020 ILLEGAL ACCESS LU 1. THE LOGICAL UNIT NUMBER SPECIFIED IN THE LU OR CS COMMAND WAS NOT A POSITIVE LOGICAL UNIT NUMBER. RE-ENTER THE CORRECTED COMMAND. OR 2. THERE IS AN LU ENTRY IN THE CARTRIDGE LIST THAT DOES NOT POINT TO A DISC DEVICE. THIS HAPPENED BECAUSE AFTER THE DISC WAS MOUNTED THE LU COMMAND WAS USED TO DO A LOGICAL UNIT SWITCH ON THE DEVICE. SWITCH THE LU BACK TO ITS DISC DEFINITION. IF DESIRED, DISMOUNT THE DISC. THE LU CAN THEN BE SWITCHED TO A NON-DISC DEVICE. "" ACCT-019 ILLEGAL ACCESS ON A SYSTEM DISC AN ATTEMPT WAS MADE TO WRITE ON A SYSTEM DISC. THE SYSTEM MANAGER IS THE ONLY USER THAT HAS THIS CAPABILITY. "" ACCT-018 ILLEGAL LU; LU NOT ASSIGNED TO SYSTEM ATTEMPT TO ACCESS AN LU THAT IS NOT ASSIGNED TO THE SYSTEM. "" ACCT-017 ILLEGAL READ/WRITE ON TYPE 0 FILE AN ATTEMPT WAS MADE TO READ, WRITE, OR POSITION A TYPE 0 FILE THAT DOES NOT SUPPORT THE OPERATION. CHECK THE FILE PARAMETERS OR THE NAMR. "" ACCT-016 ILLEGAL TYPE 0 OR FILE BLOCKSSIZE=0 ONE OF THE FOLLOWING OCCURED: 1) THE WRONG FILE TYPE WAS SPECIFIED, 2) AN ATTEMPT WAS MADE TO CREATE OR PURGE A TYPE 0 FILE, OR 3) THE SIZE SPECIFIED WAS ZERO BLOCKS. CHECK THE SIZE AND TYPE PARAMETERS. "" ACCT-015 ILLEGAL NAME THE FILE NAME DOES NOT CONFORM TO THE SYNTAX RULES. CORRECT THE NAME AND RE-ENTER THE COMMAND. "" ACCT-014 DIRECTORY FULL THERE IS NO MORE ROOM IN THE FILE DIRECTORY. PURGE ANY UNUSED FILES AND PACK THE DISC IF POSSIBLE. OTHERWISE, TRY ANOTHER CARTRIDGE. "" ACCT-013 DISC LOCKED THE CARTRIDGE SPECIFIED IS LOCKED. INITIALIZE THE CARTRIDGE IF IT WAS NOT INITIALIZED, OTHERWISE KEEP TRYING. "" ACCT-012 EOF OR SOF ERROR AN ATTEMPT WAS MADE TO READ, WRITE, OR POSITION A FILE BEYOND THE FILE BOUNDARIES. CHECK THE RECORD POSITION PARAMETERS. THE RESULTS DEPENDS ON THE FILE TYPE AND THE CALL. "" ACCT-011 DCB NOT OPEN AN ATTEMPT WAS MADE TO ACCESS AN UNOPENED DCB. USE THE CREATE OR OPEN CALL TO OPEN THE DCB AND CHECK FOR ERRORS. "" ACCT-010 NOT ENOUGH PARAMETERS ONE OR MORE OF THE REQUIRED PARAMETERS WERE OMITTED FROM THE CALL. ENTER THE REQUIRED PARAMETERS. "" ACCT-009 ATTEMPT TO USE APOSN OR FORCE A TYPE 0 FILE TO TYPE 1 A TYPE 0 FILE CANNOT BE POSITIONED WITH APOSN OR BE FORCED TO A TYPE 1 FILE. CHECK THE FILE TYPE. "" ACCT-008 FILE OPEN OR LOCK REJECTED AN ATTMPT WAS MADE TO OPEN A FILE THAT WAS ALREADY OPENED EXCLUSIVELY OR WAS ALREADY OPENED TO EIGHT PROGRAMS, OR THE CARTRIDGE CONTAINING THE FILE IS LOCKED. USE THE CL OR DL COMMAND TO LOCATE THE LOCK. IF THE FILE IS BEING PACKED, CHECK TO SEE IF SPOOLING IS SHUT DOWN. "" ACCT-007 ILLEGAL SECURITY CODE OR ILLEGAL WRITE ON LU2 OR 3 1. AN ATTEMPT WAS MADE TO ACCESS A FILE WITHOUT SPECIFYING THE SECURITY CODE OR WITH THE WRONG SECURITY CODE. FIND OUT THE CORRECT CODE AND USE IT OR DO NOT ACCESS THE FILE. OR 2. AN ATTEMPT WAS MADE BY A SESSION USER (NOT THE SYSTEM MANAGER) TO WRITE ON LU 2 OR 3. SESSION USERS DO NOT HAVE WRITE ACCESS TO LU 2 OR 3. "" ACCT-006 FILE NOT FOUND AN ATTEMPT WAS MADE TO ACCESS A FILE THAT CANNOT BE FOUND. CHECK THE FILE NAME. "" ACCT-005 RECORD LENGTH ILLEGAL AN ATTEMPT WAS MADE TO READ OR POSITION A FILE TO A RECORD THAT HAS NOT BEEN WRITTEN, OR TO WRITE AN ILLEGAL RECORD LENGTH ON AN UPDATE. CHECK THE FILE POSITION OR SIZE PARAMETER. "" ACCT-004 MORE THAN 32767 RECORDS IN A TYPE 2 FILE AN ATTEMPT WAS MADE TO CREATE A TYPE 2 FILE WITH TOO MANY RECORDS OR WITH A RECORD SIZE THAT IS TOO LARGE. CHECK THE SIZE PARAMETER. "" ACCT-003 BACKSPACE ILLEGAL AN ATTEMPT WAS MADE TO BACKSPACE A DEVICE (OR TYPE 0 FILE) THAT CANNOT BE BACKSPACED. CHECK THE DEVICE TYPE. "" ACCT-002 DUPLICATE FILE NAME A FILE ALREADY EXISTS WITH THE NAME SPECIFIED. REPEAT THE COMMAND WITH A NEW NAME OR PURGE THE EXISTING FILE. "" ACCT-001 DISC ERROR THE DISC IS DOWN. TRY AGAIN AND THEN REPORT THE PROBLEM TO THE SYSTEM MANAGER. "" L-CK SUM THIS IS A CHECKSUM ERROR. MOST LIKELY YOU SPECIFIED A FILE TO THE LOADR THAT DID NOT CONTAIN RELOCATABLE FORMAT CODE. A TYPICAL MISTAKE IS SPECIFYING THE SOURCE FILE NAME INSTEAD OF THE BINARY FILE NAME. IF THE FILE YOU SPECIFIED WAS THE CORRECT ONE THEN THAT FILE HAS BEEN OVERLAYED OR CORRUPTED. PURGE THAT FILE AND RECOMPILE THE ORIGINAL SOURCE AND TRY AGAIN. "" L-IL REC THE LOADR FOUND A RECORD THAT WAS NOT A NAM, ENT, EXT, DBL, EMA, GEN, LOD, OR END RECORD. THE CHECKSUM WAS OK BUT THE RECORD WAS UNIDENTIFIED. WAS THE FILE SPECIFIED A RELOCATABLE FILE ? TRY RECOMPILING AND LOADING. "" L-OV MEM THE SIZE OF THE CODE LOADED SO FAR EXCEEDS THE MAX SIZE THAT YOU SPECIFIED OR EXCEEDS THE LARGEST POSSIBLE SIZE FOR A PROGRAM. MAX SIZE FOR LARGE BACKGROUND (LB) NON EMA PROGRAMS IS 28K WORDS (INCLUDING BASE PAGE) AND 26K FOR LB EMA PROGRAMS. CONSULT THE GENERATION MAP FOR THE MAX SIZE OF REAL TIME AND BACKGROUND PROGRAMS. IF YOUR PROGRAM IS JUST TOO LARGE THE FOLLOWING SOLUTIONS MIGHT BE TRIED: 1. IF THE PROGRAM IS NOT TYPE 4 (LARGE BACKGROUND [LB]) MAKE IT A TYPE 4 BY SPECIFYING THE ' OP,LB ' COMMAND TO THE LOADR. 2. IF YOU SPECIFIED A SIZE, THEN DON'T SPECIFY A SIZE THE LOADR WILL DO ALL IT CAN TO MAKE YOUR PROGRAM FIT. 3. SEGMENT THE PROGRAM 4. TRY WRITING SOME OF THE PROGRAM IN ASSEMBLY 5. SEE IF THERE ARE ANY DATA DECLARATIONS THAT CAN BE REMOVED OR ANY DATA DECLARATIONS THAT CAN BE MOVED TO EMA. "" L-OV BSE BASE PAGE OVERFLOW. THIS PROGRAM HAS USED TOO MANY BASE PAGE LINKS. IF THE CP OPTION WAS NOT USED, TRY USING IT TO PUT LINKS ON THE CURRENT PAGE INSTEAD OF ALL ON THE BASE PAGE. IF THE CP OPTION WAS USED, RELOAD THE PROGRAM BUT THIS TIME SPECIFY THE 'OP, LE' OPTION. THIS WILL LIST ALL ENTRY POINTS AND THE BASE PAGE LINKAGES. THIS LOAD WILL ALSO FAIL, HOWEVER, NOW YOU KNOW WHICH MODULES ARE USING UP ALL THE LINKS. BY USING THE LO,XXXXX COMMAND AND ALIGNING THOSE MODULES TO PAGE BOUNDARIES THE LINKAGE NEEDS CAN BE REDUCED. ALTERNATELY YOU MAY WISH TO REARRANGE THE LOADING ORDER OF YOUR SUBROUTINES. THIS MAY IMPROVE (OR MAKE WORSE) THE LINKAGE NEEDS OF YOUR PROGRAM. "" L-OV SYM THIS IS A SYMBOL TABLE OVERFLOW. THE LOADR NEEDS MORE ROOM FOR ITS INTERNAL SYMBOL TABLE AND FIX UP TABLE. SINCE THE LOADR IS A TYPE 4 PROGRAM IT CAN BE MADE AS LARGE AS THE LARGEST NORMAL BACKGROUND PARTITION. TO GIVE THE LOADR MORE ROOM USE THE ' SZ ' OPERATOR COMMAND. THAT IS, *SZ,LOADR,XX XX = # OF PAGES OR FROM FMGR, :SYSZ,LOADR,XX BY INCREASING THE SPACE FOR THE LOADR THE L-OV SYM PROBLEM SHOULD BE SOLVED. CONSULT THE RTE-IVB TERMINAL USER'S REFERENCE MANUAL FOR MORE INFORMATION ON THE 'SZ ' COMMAND. IF THE SZ COMMAND DOES NOT SOLVE THE PROBLEM, THEN TRY USING THE LOADR ' SE ' COMMAND AFTER EVERY LOADR 'RE' COMMAND. THIS WILL REDUCE SPACE NEEDED FOR FIXUPS. IN ADDITION TO USING THE 'SE' COMMAND AFTER EVERY 'RE' COMMAND, TRY LOADING A NUMBER OF YOUR SUBROUTINES (STILL DOING 'SE') BEFORE THE MAIN OF THE PROGRAM. "" L-CM BLK THIS IS A COMMON BLOCK ERROR. THIS ERROR OCCURS IF THE LARGEST COMMON DECLARATION OF A PROGRAM DOES NOT APPEAR IN THE FIRST MODULE OF THE PROGRAM LOADED. PROGRAMS THAT USE COMMON MUST DECLARE THAT COMMON IN THE FIRST ROUTINE LOADED AND THAT COMMON DECLARATION MUST BE THE LARGEST ENCOUNTERED IN THE LOAD. THIS ERROR IS ALSO GENERATED IF THE AMOUNT OF COMMON REQUESTED EXCEEDS THAT WHICH IS AVAILABLE. "" L-DU ENT DUPLICATE ENTRY POINT. GENERALLY THIS OCCURS WHEN THE SAME SUBROUTINE WAS LOADED TWICE. ALTERNATELY YOU NAMED A SUBROUTINE WITH THE SAME NAME (ENT IN ASMB) THAT WAS ALREADY BEING USED SOMEWHERE ELSE WITHIN THE PROGRAM THAT YOU WERE TRYING TO LOAD. CONFUSION SOMETIMES OCCURS WITH SEGMENTED PROGRAMS. A SUBROUTINE LOADED WITH THE MAIN MUST NOT BE AGAIN LOADED WITH A SEGMENT. LOOK AT THE LOAD MAP FOR THE LOAD. DID YOU TRY TO LOAD THE SUBROUTINE WITH A SEGMENT WHERE THAT SUBROUTINE WAS ALREADY LOADED WITH THE MAIN ? THE LOAD MAP WILL LIST ALL SUBROUTINES LOADED WITH THE MAIN. "" L-TR ADD NO TRANSFER ADDRESS. ONLY SUBROUTINES WERE LOADED. THE LOADR COULD NOT TELL WHICH MODULE OF THE PROGRAM WAS THE MAIN AND WHICH ONES WERE SUBROUTINES. IF THE PROGRAM WAS WRITTEN IN FORTRAN NO MODULES WERE FOUND THAT CONTAINED THE 'PROGRAM XXXXX' STATEMENT. IF THE PROGRAM WAS WRITTEN IN ASMB YOU PROBABLY FORGOT TO PUT A LABEL ON THE END STATEMENT. IN ASMB THE MAIN OF A SEGMENT OR OF A PROGRAM IS DIFFERENTIATED FROM SUBROUTINES BY PLACING THE LABEL OF WHERE THE PROGRAM OR SEGMENT IS TO START EXECUTION AS THE OPERAND OF THE END STATEMENT. IF MULTIPLE ROUTINES HAVE LABELS ON THE END STATEMENT THE FIRST ONE ENCOUNTERED IS USED AS THE MAIN OF THE PROGRAM. "" L-RE SEQ RECORD OUT OF SEQUENCE. THE LOADR WAS RELOCATING AND ENCOUNTERED RECORDS IN THE WRONG ORDER. RELOCATABLE RECORDS ARE IN THE ORDER OF GEN/LOD, NAM, ENT, EXT, DBL, AND END. GENERALLY THIS ERROR OCCURS WHEN RELOCATING FROM AN LU, SAY A MAG TAPE, AND THE TAPE IS INCORRECTLY POSITIONED. IF THE RELOCATION WAS FROM A FILE, RECOMPILE THE SOURCE AND TRY AGAIN, AS THE FILE IS CORRUPT. "" L-IL PRM THE RUN STRING SUBMITTED TO THE LOADER WAS IN ERROR. TRY AGAIN. "" L-CO RES ATTEMPT TO REPLACE A MEMORY RESIDENT PROGRAM. YOU TRIED TO REPLACE A MEMORY RESIDENT PROGRAM. THIS IS ILLEGAL. "" L-OV FIX THIS IS A FIXUP TABLE OVERFLOW. THE LOADR NEEDS MORE ROOM FOR ITS INTERNAL SYMBOL TABLE AND FIX UP TABLE. SINCE THE LOADR IS A TYPE 4 PROGRAM IT CAN BE MADE AS LARGE AS THE LARGEST NORMAL BACKGROUND PARTITION. TO GIVE THE LOADR MORE ROOM USE THE ' SZ ' OPERATOR COMMAND. THAT IS, *SZ,LOADR,XX XX = # OF PAGES OR FROM FMGR, :SYSZ,LOADR,XX BY INCREASING THE SPACE FOR THE LOADR THE L-OV SYM PROBLEM SHOULD BE SOLVED. CONSULT THE RTE-IVB TERMINAL USER'S REFERENCE MANUAL FOR MORE INFORMATION ON THE ' SZ ' COMMAND. IF THE SZ COMMAND DOES NOT SOLVE THE PROBLEM, THEN TRY USING THE LOADR ' SE ' COMMAND AFTER EVERY LOADR 'RE' COMMAND. THIS WILL REDUCE SPACE NEEDED FOR FIXUPS. IN ADDITION TO USING THE 'SE' COMMAND AFTER EVERY 'RE' COMMAND, TRY LOADING A NUMBER OF YOUR SUBROUTINES (STILL DOING 'SE') BEFORE THE MAIN OF THE PROGRAM. "" L-LM LIB THE LIMIT ON THE NUMBER OF LIBRARIES SPECIFIED BY THE 'LI' COMMAND HAS BEEN EXCEEDED. YOU MAY SPECIFY 10 LIBRARIES. INSTEAD OF SPECIFYING ANOTHER LIBRARY YOU CAN SPECIFICALLY DO A 'SE' OF THE FILE. "" L-IL REL THE COMPILER PRODUCED AN ILLEGAL RECORD. ONE OF THE FOLLOWING OCCURRED: THE NUMBERS OF ENTRIES SPECIFIED IN AN ENT OR EXT RECORD WAS ZERO. THE NUMBER OF INSTRUCTION WORDS SPECIFIED IN A DBL RECORD WAS ZERO. A RELOCATABLE INDICATOR IN A DBL RECORD WAS SEVEN. A DBL RECORD WAS PRODUCED THAT REFERENCED AN EXTERNAL BUT THAT EXTERNAL WAS NOT IN ANY OF THE EXT RECORDS. ALL OF THE ABOVE ARE IMPOSSIBLE CONDITIONS. RECOMPILE AND TRY AGAIN. THIS COULD ALSO BE A COMPILER BUG. "" L-IL PTN YOU SPECIFIED A PARTITION IN THE LOAD OF THE PROGRAM, HOWEVER, THAT PARTITION DOES NOT EXIST OR HAS BEEN DOWNED DUE TO A PARITY ERROR. TRY AGAIN, THIS TIME SPECIFY A PARTITION THAT EXISTS OR DON'T SPECIFY ANY PARTITION AT ALL. "" L-RQ PGS THE NUMBER OF PAGES THAT YOU SPECIFIED IN THE LOAD OF THE PROGRAM EXCEEDS THAT NUMBER OF PAGES IN THE PARTITION YOU SPECIFIED. EITHER SPECIFY A DIFFERENT PARTITION OR NO PARTITION AT ALL. "" L-OV PTN THE SPECIFIED PROGRAM SIZE IS TOO LARGE FOR THE PARTITION. EITHER SPECIFY A SMALLER SIZE OR NO SIZE AT ALL. SEE ALSO L-OV MEM ERROR FOR OTHER ALTERNATIVES. "" L-ML EMA ILLEGAL EMA DECLARATION. TWO DIFFERENT EMA LABELS WERE USED, OR THE EMA DECLARATION WAS NOT MADE IN THE MAIN OF A PROGRAM AND THAT MAIN LOADED FIRST, OR AN EMA LABEL WAS ALSO DECLARED AS AN ENTRY POINT IN ANOTHER MODULE. THE EMA DECLARATION MUST BE IN THE MAIN OF THE PROGRAM AND THAT MAIN MUST BE THE FIRST MODULE LOADED. THE EMA STATEMENT MUST BE IN ANY SEGMENT OR SUBROUTINE REFERENCING ANY ELEMENT IN EMA. "" L-ID EXT NO ID EXTENSIONS AVAILABLE FOR THE EMA PROGRAM. YOU MUST FREE UP SOME ID EXTENSIONS BEFORE THE EMA PROGRAM CAN BE SUCCESSFULLY LOADED. "" L-SZ EMA THE PROGRAMS DECLARED EMA SIZE IS TOO LARGE FOR THIS SYSTEMS PARTITIONS DEFINITION, IE THERE IS NO EXISTING PARTITION LARGE ENOUGH TO RUN THIS PROGRAM. EITHER REBOOT AND RECONFIGURE SYSTEM TO ALLOW MORE EMA SPACE OR DECLARE LESS EMA SPACE IN THE PROGRAM. "" L-SS ENT YOU ATTEMPTED TO ACCESS AN SSGA ENTRY POINT BUT YOU DID NOT ASK FOR SSGA AT THE BEGINNING OF THE LOAD. RELOAD THE PROGRAM BUT THIS TIME DO A 'OP,SS' AT THE BEGINNING OF THE LOAD. "" L-IL CMD ATTEMPT TO PURGE A PROGRAM UNDER BATCH OR ATTEMPT TO USE THE 'LI' OR 'PU' COMMANDS WITHIN A LOADR COMMAND FILE. LI AND PU COMMANDS ARE NOT ALLOWED WITHIN A LOADR COMMAND FILE UNLESS THAT COMMAND FILE IS AN INTERACTIVE DEVICE (IE A TTY OR CRT). "" L-ID SEG NOT ENOUGH LONG AND SHORT ID SEGMENTS TO FINISH THE LOAD. THIS IS AN EXTREMELY RARE ERROR. THE LOADR WAS CREATING ID SEGMENTS AND THERE WERE ENOUGH ID SEGMENTS AT THE BEGINNING TO FINISH THE LOAD, HOWEVER, BETWEEN CREATING ONE ID SEGMENT AND CREATING THE NEXT ALL OTHER ID SEGMENTS WERE USED UP (MAYBE ANOTHER LOADR OR FILE MANAGER GOT THEM) AT ANY RATE THERE AREN'T ENOUGH TO FINISH THE LOAD. THE PROPER RESPONSE TO THIS ERROR IS TO ' OF ' OR PURGE ALL SEGMENTS AND THE MAIN OF THE LOAD THAT WAS JUST UNSUCCESSFUL, FREE UP SOME ADDITIONAL ID SEGMENTS AND TRY THE LOAD AGAIN. IF ENOUGH ID SEGMENTS ARE FREED UP THE LOAD WILL SUCCEED. THIS ERROR COULD ONLY OCCUR IN SEGMENTED LOADS. "" L-RF EMA ATTEMPT TO ACCESS AN EMA EXTERNAL WITH OFFSET OR INDIRECT. IF THIS IS A FORTRAN PROGRAM YOU MORE THAN LIKELY FORGOT TO PUT THE $EMA STATEMENT IN A SUBROUTINE THAT ACCESSED AN EMA ELEMENT. IF THE PROGRAM WAS WRITTEN IN ASMB USE THE H-P SUPPLIED ROUTINES .EMAP AND .EMIO TO MAP IN THE ARRAYS AND THEN INDEX INTO THE ARRAY VIA THE ADDRESS RETURNED, NOT VIA A REFERENCE TO THE EMA LABEL. "" L-UN EXT UNDEFINED EXTERNALS EXIST WHICH PROHIBITS THE LOAD FROM COMPLETING. AN UNDEFINED EXTERNAL IS A REFERENCE MADE BY THE ROUTINE YOU ARE LOADING TO ANOTHER ROUTINE. FOR EXAMPLE IF YOUR FORTRAN PROGRAM HAD THE FOLLOWING CODE : CALL XYZ(I,J,K) THEN THE SUBROUTINE XYZ WOULD BE AN EXTERNAL. THE PROBLEM YOU HAVE IS THAT YOU LOADED THE ROUTINE THAT CONTAINED THE CALL TO XYZ BUT YOU DIDN'T LOAD THE XYZ SUBROUTINE ITSELF. XYZ IS THE UNDEFINED EXTERNAL. THE PROPER COURSE HERE IS TO RELOAD YOUR PROGRAM BUT THIS TIME DON'T FORGET TO LOAD THE ROUTINES LISTED WHEN THE LOADR ABORTED THE LAST TIME YOU TRIED TO LOAD THE PROGRAM. ONE LAST POINT. IT IS POSSIBLE TO FORCE LOAD A PROGRAM OR SEGMENTS THAT HAVE UNDEFINED EXTERNALS. THIS IS DONE WITH THE LOADR 'FORCE' COMMAND. HOWEVER, IF YOU FORCE LOAD THE PROGRAM IT IS YOUR RESPONSIBILITY TO MAKE SURE THAT THE LINE OF CODE THAT REFERENCES THE EXTERNAL IS NEVER EXECUTED. THAT IS, MAKE SURE THAT THE CALL TO XYZ IS NOT EXECUTED OR YOUR PROGRAM WILL PROBABLY BE ABORTED WITH A DM OR MP ERROR. "" L-EX CPY ATTEMPT TO REPLACE OR PURGE A PROGRAM WHERE COPIES OF THAT PROGRAM EXIST. IT IS NOT POSSIBLE TO REPLACE OR PURGE A PROGRAM FROM THE SYSTEM IF COPIES OF THAT PROGRAM EXIST. THE PROBLEM HERE IS THAT OTHER COPIES OF THE SAME PROGRAM EXIST AND MAY BE IN USE. THE PROPER COURSE HERE IS TO DO AN ' OF,PROG,8 ' ON ALL THE PROGRAMS LISTED AS COPIES. THIS WILL GET RID OF THOSE PROGRAMS SO THAT YOU CAN PERFORM THE PROGRAM PURGE OR REPLACE. NOTE THAT THIS PROCESS SHOULD ONLY BE DONE BY THE SYSTEM MANAGER. "" L-RP CPY ATTEMPT TO REPLACE A COPIED PROGRAM. YOU TRIED TO DO A PROGRAM REPLACE ON A PROGRAM THAT WAS A COPY OF ANOTHER PROGRAM. REPLACEMENT OPERATIONS MAY ONLY BE DONE ON THE ORIGINAL PROGRAM NOT THE COPIED PROGRAM. THE PROPER THING TO DO NOW IS EDIT THE SOURCE OF YOUR PROGRAM AND MAKE SURE THE NAME IS THE ORIGINAL PROGRAM NAME. "" L-PE LDR TRYING TO DO A PURGE OR PERMANENT LOAD WITH A COPY OF THE LOADR. RE-RUN THE LOADR USING THE REAL PROGRAM: RU,LOADR:IH. "" L-DU PGM THIS PROBLEM RESULTS WHEN YOU TRY TO LOAD THE SAME PROGRAM SEVERAL TIMES BUT DO NOT GET RID OF THE EARLIER LOADS. FOR EXAMPLE, YOU LOADED A PROGRAM CALLED XXXXX AND FOR SOME REASON LOADED THE SAME PROGRAM AGAIN. IN THIS CASE THE LOADR WARNED YOU WITH A W-DU PGM WARNING MESSAGE AND THEN RENAMED YOUR PROGRAM TO ..XXX. THAT IS THE LOADR FORGIVES YOU THE FIRST TIME. HOWEVER, YOU HAVE NOW LOADED A PROGRAM WITH THE SAME NAME A THIRD TIME. THE LOADR WILL NOT FORGIVE THIS AGAIN. THE SOLUTION IS TO DO A :OF,XXXXX,8 :OF,..XXX,8 AND NOW START THE LOAD OVER AGAIN. "" L-NO IDS NOT ENOUGH ID SEGMENTS TO FINISH THE LOAD. YOUR SYSTEM HAS RUN OUT OF ID SEGMENTS. CALL THE SYSTEM MANAGER TO FREE UP SOME ID SEGMENTS. HE WILL PROBABLY USE THE OFF COMMAND TO PURGE SOME PROGRAMS FROM THE SYSTEM. "" L-RP PGM YOU TRIED TO REPLACE A PERMANENT PROGRAM. HOWEVER, THAT PROGRAM TERMINATED SERIALLY REUSABLE, SAVING RESOURCES, OR WAS OPERATOR SUSPENDED. THAT IS, THE PROGRAM STILL OWNED A SYSTEM PARTITION. OFF THE PROGRAM AND REPEAT THE LOAD. ""