READ 011 READT REJECTED THE SIZE (NUMBER OF TRACKS) YOU SPECIFIED BECAUSE IT'S OF A BAD FORMAT (E.G. NEGATIVE VALUE) OR THE SIZE REQUESTED IS NOT LARGE ENOUGH TO RESTORE THE CARTRIDGE ON MAG TAPE. "" READ 012 THE ROUTINE READT USES TO MOUNT A CARTRIDGE DETECTED AN ERROR. THIS ERROR IS RETURNED IN THE FMGR FORMAT. THE FOLLOWING ARE POSSILBE ERROR CONDITIONS. FIND THE ONE THAT APPLYS TO YOU AN DO AS SUGGESTED. FMGR 012 DUPLICATE LABEL OR CRN ALREADY MOUNTED. HAVE THAT DISC OR CRN REMOVED THEN RUN READT AGAIN. FMGR 056 THE SIZE REQUESTED IS TOO LARGE FOR THE DISC LU SPECIFIED. RUN READT AGAIN WITH A SMALLER SIZE PARAMTER. FMGR 063 YOU CURRENTLY HAVE MOUNTED THE MAXIMUM NUMBER OF DISC CARTRIDGES IN YOUR SESSION. REMOVE ONE AND RUN READT AGAIN. FMGR 064 THERE ARE PRESENTLY NO MORE FREE DISC LUS IN THE DISC POOL. HAVE SOMEONE RELEASE A CARTRIDGE THAT THEY ARE NOT CURRENTLY USING. FMGR 065 THERE IS A CONFLICT IN SST DEFINITION. YOU ARE TRYING TO MOUNT A DISC LU THAT HAS A SESSION LU NUMBER ASSIGNED TO TO SOME OTHER DEVICE. CHECK YOUR SST AND FIND OUT TO WHAT LU THAT NUMBER IS ASSIGNED, THEN CHANGE IT OR CHOOSE ANOTHER DISC LU. FMGR 066 THERE IS NO MORE ROOM IN YOUR SST TO PLACE AN ENTRY. REMOVE AN ENTRY FROM YOUR SST IF POSSIBLE. IF THAT'S NOT DESIRABLE THEN CALL SYSTEM MANAGER. "" READ 013 THE DESIRED DISC LU OR THE AVAILABLE FREE LUS IN THE DISC POOL ARE NOT LARGE ENOUGH TO RESTORE THE CARTRIDGE THAT'S ON MAG TAPE. "" READ 014 THE FMP TRACKS ON LU 2 OR LU 3 (IF 3 EXISTS) ARE NOT RESTORABLE WITH READT. "" READ 015 BAD TRANSMISSION -- MEMORY TO DISC TRK XXX SEC YYY READT TRIED TO TRANSFER DATA FROM MEMORY TO A DISC LU. DURING THIS PROCESS A CHECK OF THE TRANSMISSION LOG SHOWED AN UNEXPECTED VALUE. RUN READT AGAIN, IF IT HAPPENS ONCE MORE CALL YOUR SYSTEM MANAGER. "" READ 016 BAD TRANSMISSION -- MAG TAPE TO MEMORY REC XXX READT DETECTED AN ERROR IN TRANSMISSION OF DATA FROM THE MAG TAPE UNIT INTO MEMORY. TRY READING THE TAPE AGAIN. IF IT HAPPENS ONCE MORE CALL YOUR SYSTEM MANAGER. "" WRIT 001 THE REQUESTED MAG TAPE UNIT IS DOWN. BY UPPING THE APPROPRIATE EQT THE DEVICE CAN BE ENABLED. "" WRIT 002 ONLY THE SYSTEM MANAGER CAN SAVE SYSTEM DISCS. "" WRIT 003 THE MAG TAPE YOU WISH TO USE IS LOCKED TO SOME PROCESS. FIND OUT WHO CURRENTLY HAS THE MAG TAPE LOCKED (E.G. RU,WHZAT) AND WAIT UNTIL IT'S RELEASED OR HAVE THE USER RELEASE IT FOR YOU. "" WRIT 004 THE PARAMETER DESCRIBING THE DESIRED MAG TAPE UNIT DOES NOT SATISFY READT'S REQUIREMENTS FOR A LEGAL MAG TAPE UNIT. THE POSSIBLE CAUSES FOR THIS ERROR INCLUDE: 1.THE SPECIFIED MAG TAPE LU IS NOT BETWEEN -63 AND +63. 2. THE DRIVER OF THE SPECIFIED LU IS NOT A MAG TAPE DRIVER. "" WRIT 005 THE DESIRED MAG TAPE UNIT IS OFF-LINE. THE ON-LINE BUTTON MUST BE DEPRESSED TO ENABLE THE ON-LINE SWITCH. "" WRIT 006 A WRITE RING IS REQUIRED TO WRITE INFORMATION ON A MAG TAPE. PLACE A WRITE RING ON THE TAPE SPOOL AND RUN WRITT AGAIN. "" WRIT 007 THE DRIVER DETECTED A PARITY ERROR WHEN READING FROM THE MAG TAPE. TRY AGAIN, IF IT OCCURS AGAIN THEN THE TAPE MAY BE IRRECOVERABLE. CALL SYSTEM MANAGER. "" WRIT 008 THE END OF TAPE WAS REACHED. MOUNT THE FOLLOWING TAPE TO WRITE THE REMAINING PORTIONS OF THE CARTRIDGE. TO CONTINUE THE PROGRAM ENTER "GO". TO HALT THE PROCESS ENTER "AB". NOTE HOWEVER THAT A RESPONSE OF AN "AB" WILL PLACE A PARTIALLY COMPLETED CARTRIDGE ON YOUR TAPE. "" WRIT 009 THE DESIRED CARTRIDGE HAS A FILE OPEN OR THE CARTRIDGE IS LOCKED TO ANOTHER PROGRAM. TRY DOING A DL ON THAT CARTRIDGE AND FIND OUT WHAT'S LOCKING THE PROGRAM OR WHAT FILE IS OPEN. "" WRIT 010 THE DESIRED CARTRIDGE OR DISC LU COULD NOT BE FOUND. DO A CL (CARTRIDGE LIST) TO MAKE SURE THAT WHAT YOU'RE SEEKING IS REALLY THERE. "" WRIT 011 WRITT REJECTED THE USE OF THE SPECIFIED DISC LU. THERE ARE A VARIETY OF REASONS FOR THIS, THEY INCLUDE: 1.THE DISC LU NUMBER MUST BE A NEGATIVE NUMBER BUT NO SMALLER THAN -63. 2.THE DESIRED DISC LU IS NOT IN YOUR SST. 3.THE DRIVER TYPE OF THE REQUESTED DISC LU IS NOT A DISC DRIVER. "" WRIT 012 YOU CANNOT SAVE FMP TRACKS OFF LU 2 OR LU 3 (IF 3 EXITS) WITH WRITT. "" WRIT 013 WRITT TRIED TO READ DATA FROM A DISC LU INTO MEMORY AND FOUND THE TRANMISSION IRREGULAR. RUN WRITT AGAIN, IF THE SITUATION OCCURS ONCE MORE THERE MAY BE A BAD TRACK ON THAT DISC LU. SAVE AS MUCH DATA AS YOU CAN AND NOTIFY YOUR SYSTEM MANAGER. "" WRIT 014 THE TRANSMISSION OF DATA FROM MEMORY TO MAG TAPE MAY BE FAULTY. RUN WRITT AGAIN, IF IT HAPPENS ONCE MORE CALL YOUR SYSTEM MANAGER. "" DM MAPPING ERROR. AN ATTEMPT WAS MADE TO READ/WRITE OUTSIDE OF THE MAPPED ADDRESS SPACE. "" MP MEMORY PROTECT ERROR. THE CALL WAS NOT AN EXEC, $L1BR, OR $L1BX CALL. "" RE A RE-ENTRANT SUBROUTINE ATTEMPTED TO CALL ITSELF. "" RQ AN ILLEGAL REQUEST CODE IS SPECIFIED IN AN EXEC CALL. "" TI A BATCH PROGRAM EXCEEDS THE ALLOWED TIME. "" SC00 A BATCH PROGRAM ATTEMPTED TO SUSPEND (EXEC(7)). "" SC01 MISSING PARAMETER. "" SC02 ILLEGAL PARAMETER "" SC03 THE SPECIFIED PROGRAM CANNOT BE SCHEDULED. "" SC04 THE SPECIFIED PROGRAM IS NOT A SUBORDINATE (OR "SON") TO THE PROGRAM ISSUING THE COMPLETION CALL. "" SC05 THE PROGRAM GIVEN IS NOT DEFINED. "" SC06 NO RESOLUTION CODE IS SPECIFIED IN THE EXECUTION TIME EXEC CALL. "" SC07 A PROHIBITED CORE LOCK WAS ATTEMPTED. "" SC08 THE PROGRAM JUST SCHEDULED IS ASSIGNED TO A PARTITION SMALLER THAN THE PROGRAM ITSELF OR TO AN UNDEFINED PARTITION. UNASSIGN THE PROGRAM OR REASSIGN THE PROGRAM TO A PARTITION THAT IS AS LARGE OR LARGER THAN THE PROGRAM. "" SC09 THE PROGRAM JUST SCHEDULED IS TOO LARGE FOR ANY PARTITION OF THE SAME TYPE. FOR EXAMPLE, TRYING TO SCHEDULE A 23K BACKGROUND PROGRAM WHEN THE LARGEST BACKGROUND PARTITION IS ONLY 21K. "" SC10 THERE IS NOT ENOUGH SYSTEM AVAILABLE MEMORY FOR THE STRING PASSAGE. "" SC11 EXEC SCHEDULE OR TIMED EXECUTION REQUEST WAS ISSUED AND PROGRAM SPECIFIED IS ALREADY IN THE TIME LIST FOR ANOTHER SESSION. "" RN00 THERE ARE NO OPTION BITS SET IN THE CALL. "" RN01 NOT USED "" RN02 THE SPECIFIED RESOURCE NUMBER IS NOT DEFINED. "" RN03 AN UNAUTHORIZED ATTEMPT WAS MADE TO CLEAR A LOCAL RESOURCE NUMBER. "" LU01 A PROGRAM HAS ONE OR MORE LOGICAL UNITS LOCKED AND IS TRYING TO LOCK ANOTHER WITH WAIT. "" LU02 ILLEGAL LOGICAL UNIT REFERENCE. THE LU SPECIFIED IS EITHER 1) ILLEGAL OR NON-EXISTENT FOR THE CURRENT SESSION/SYSTEM CONFIGURATION, OR 2) A DISK LU, BUT THE "DISK ALSO" BIT WAS NOT SET IN THE LU LOCK REQUEST. "" LU03 NOT ENOUGH PARAMETERS ARE FURNISHED IN THE CALL. LOGICAL UNIT REFERENCE LESS THAN ONE. LOGICAL UNIT NOT LOCKED TO CALLER. "" LU04 TRYING TO LOCK A LOGICAL UNIT NOT DEFINED IN CALLER'S SST. "" DR01 NOT ENOUGH PARAMETERS WERE SPECIFIED. "" DR02 THE NUMBER OF TRACKS IS <= ZERO OR AN ILLEGAL LOGICAL UNIT WAS SPECIFIED. "" DR03 AN ATTEMPT TO RELEASE A TRACK ASSIGNED TO ANOTHER PROGRAM WAS MADE. "" IO00 AN ILLEGAL CLASS NUMBER WAS SPECIFIED. OUTSIDE TABLE, NOT ALLOCATED, OR BAD SECURITY CODE. "" IO01 NOT ENOUGH PARAMETERS WERE SPECIFIED. "" IO02 AN ILLEGAL LOGICAL UNIT NUMBER WAS SPECIFIED. "" IO03 ILLEGAL EQT REFERENCED BY LU IN I/O CALL (SELECT CODE=0). "" IO04 AN ILLEGAL USER BUFFER WAS SPECIFIED. EXTENDS BEYOND RT\BG AREA OR NOT ENOUGH SYSTEM AVAILABLE MEMORY TO BUFFER THE REQUEST. "" IO05 AN ILLEGAL DISC TRACK OR SECTOR WAS SPECIFIED. "" IO06 A REFERENCE WAS MADE TO A PROTECTED TRACK OR TO UNASSIGNED LG TRACKS. "" IO07 THE DRIVER HAS REJECTED THE CALL. "" IO08 THE SPECIFIED DISC TRANSFER IS LONGER THAN ONE TRACK. "" IO09 THE LG TRACKS OVERFLOWED. "" IO10 CLASS GET CALL ISSUED WHILE ONE CALL ALREADY OUTSTANDING. "" IO11 A TYPE 4 PROGRAM MADE AN UNBUFFERED I/O REQUEST TO A DRIVER THAT DID NOT DO ITS OWN MAPPING. "" IO12 AN I\O REQUEST SPECIFIED A LOGICAL UNIT NOT DEFINED FOR USE BY THIS SESSION. THE "SL" COMMAND WILL REPORT ALL LOGICAL UNITS AVAILABLE TO YOUR SESSION. "" IO13 AN I/O REQUEST SPECIFIED AN LU WHICH WAS EITHER LOCKED TO ANOTHER PROGRAM, OR POINTED TO AN EQT WHICH WAS LOCKED TO ANOTHER PROGRAM. "" IO20 READ ATTEMPTED ON WRITE ONLY SPOOL FILE. REVISE PROGRAM CALL TO SPOPN OR CHECK "SL" COMMAND PARAMETERS. "" IO21 READ ATTEMPTED PAST END-OF-FILE. REVISE PROGRAM AND RE-RUN. "" IO22 SECOND ATTEMPT TO READ JCL CARD FROM BATCH INPUT FILE BY OTHER THAN FMGR. REVISE PROGRAM AND RE-RUN. "" IO23 WRITE ATTEMPTED ON READ ONLY SPOOL FILE. REVISE PROGRAM CALL TO SPOPN OR CHECK "SL" COMMAND PARAMETERS. "" IO24 WRITE ATTEMPTED BEYOND END-OF-FILE; USUALLY, SPOOL FILE OVERFLOW. OBTAIN MORE SPOOL ROOM ON DISC (SEE PK COMMAND IN BATCH SPOOL MANUAL) OR DO NOT USE SPOOLING AT THIS TIME. "" IO25 ATTEMPT TO ACCESS SPOOL LU THAT IS NOT CURRENTLY SET UP. MAY BE CAUSED BY GASP KS COMMAND - IF OTHER REASON CORRECT OFFENDING PROGRAMS. "" IO26 I/O REQUEST MADE TO A SPOOL THAT HAS BEEN TERMINATED BY THE GASP KS COMMAND. RESET THE SESSION LOGICAL UNIT WITH THE "CS" OR "SL" COMMAND. "" IOET AN END-OF-TAPE CONDITION OCCURRED ON THE SPECIFIED LU. CORRECT THE CONDITION AND SET THE EQT UP. "" IONR THE SPECIFIED LU IS NOT READY. MAKE THE DEVICE READY AND SET THE EQT UP. "" IOTO THE SPECIFIED LU HAS TIMED OUT. EXAMINE THE DEVICE, CORRECT THE PROBLEM, AND SET THE EQT UP. "" IOPE A PARITY ERROR OCCURRED IN THE DATA TRANSMISSION FROM THE SPECIFIED LU. EXAMINE THE DEVICE, CORRECT THE PROBLEM, AND SET THE EQT UP. "" ILL INT AN ILLEGAL INTERRUPT OCCURRED ON THE SPECIFIED CHANNEL. "" L 01 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 02 THE LOADR FOUND A RECORD THAT WAS NOT A NAM, ENT, EXT, DBL, EMA, OR END RECORD. THE CHECKSUM WAS OK BUT THE RECORD WAS UNIDENTIFIED. WAS THE FILE SPECIFIED A RELOCATABLE FILE ? TRY RECOMPILING AND LOADING. "" L 03 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 BACKROUND (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 BACKROUND [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 04 BASE PAGE OVERFLOW. THIS PROGRAM HAS USED TOO MANY BASE PAGE LINKS. 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 ALLIGNING 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 05 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 BACKROUND 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 05 PROBLEM SHOULD BE SOLVED. CONSULT THE RTE IV PROGRAMMERS 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 06 THIS IS A COMMON BLOCK ERROR. THIS ERROR ONLY 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. "" L 07 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 08 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 09 RECORD OUT OF SEQUENCE. THE LOADR WAS RELOCATING AND ENCOUNTERED RECORDS IN THE WRONG ORDER. RELOCATIBLE RECORDS ARE IN THE ORDER OF 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 10 THE RUN STRING SUBMITTED TO THE LOADER WAS IN ERROR. TRY AGAIN. "" L 11 ATTEMPT TO REPLACE A MEMORY RESIDENT PROGRAM. YOU TRIED TO REPLACE A MEMORY RESIDENT PROGRAM. THIS IS ILLEGAL. "" L 14 THE COMPILER PRODUCED AN ILLEGAL RECORD. A DBL RECORD WAS PRODUCED THAT REFERENCED AN EXTERNAL BUT THAT EXTERNAL WAS NOT IN ANY OF THE EXT RECORDS. THIS IS AN IMPOSSIBLE CONDITION. RECOMPILE AND TRY AGAIN. THIS COULD ALSO BE A COMPILER BUG. "" L 16 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 17 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 18 THE SPECIFIED PROGRAM SIZE IS TOO LARGE FOR THE PARTITION. EITHER SPECIFY A SMALLER SIZE OR NO SIZE AT ALL. SEE ALSO L 03 ERROR FOR OTHER ALTERNATIVES. "" L 19 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 20 NO ID EXTENSIONS AVAILABLE FOR THE EMA PROGRAM. YOU MUST FREE UP SOME ID EXTENSIONS BEFORE THE EMA PROGRAM CAN BE SUCCESSFULLY LOADED. "" L 21 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 24 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 25 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 26 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 BEGINING 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 27 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 28 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 29 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 30 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 31 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 32 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 32 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 33 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 34 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. "" CL- 01 THE INPUT TO THE COMPL & CLOAD PROGRAMS MUST BE A SOURCE FILE. THESE PROGRAMS DO NOT ACCEPT INPUT FROM AN LU. THUS THE ANSWER TO THE PROMPT NAMR(S),NAMR(L),NAMR(R), MUST NOT CONTAIN AN LU FOR THE 1ST PARAMETER IE THE SOURCE NAMR. "" CL- 02 NO CONTROL STATEMENT WAS SPECIFIED SO COMPL OR CLOAD OPENED THE SOURCE FILE TO FIND OUT WHICH LANGUAGE TO INVOKE (IE FTN4, ASMB). AN FMP ERROR WAS DETECTED ON THE OPEN REQUEST. THIS FMP ERROR WAS LISTED ALONG WITH THE CL- 02 ERROR MESSAGE. "" CL- 03 NO CONTROL STATEMENT WAS SPECIFIED SO COMPL OR CLOAD OPENED THE SOURCE FILE TO FIND OUT WHICH LANGUAGE TO INVOKE (IE FTN4,ASMB). WHILE SCANNING THE FILE FOR THE CONTROL STATEMENT AN FMP READ ERROR OCCURED. THIS ERROR WAS LISTED ALLONG WITH THE CL- 03 ERROR MESSAGE. "" CL- 04 NO CONTROL STATEMENT WAS SPECIFIED SO COMPL OR CLOAD OPENED THE SOURCE FILE TO FIND OUT WHICH LANGUAGE TO INVOKE (IE FTN4,ASMB). THAT CONTROL STATEMENT MAY OR MAY NOT HAVE BEEN FOUND. HOWEVER, AN FMP ERROR WAS DETECTED DURING THE CLOSE OF THE FILE. THAT ERROR WAS LISTED ALONG WITH THE CL- 04 MESSAGE. "" CL- 05 COMPL & CLOAD RECOGNIZE THE EXISTENCE OF ALL H-P SUPPLIED LANGUAGES AND SOME NOT SUPPLIED BY H-P. THE LANGUAGES IT RECOGNIZES ARE FTN4, PASCL, ASMB, COBOL, RPG, MICRO, SPL, ALGOL, HPAL, AND SNOBL. THE CONTROL STATEMENT MUST BE SPELLED EXACTLY AS SHOWN. IF NO CONTROL STATEMENT WAS SPECIFIED AND THE CONTROL STATEMENT OF THE PROGRAM WAS NOT IN THE FIRST 10 LINES OF THE PROGRAM, THEN A CL- 05 ERROR WILL RESULT. "" CL- 06 THE LANGUAGE REQUESTED WAS FOUND AND INVOKED BY COMPL OR CLOAD, HOWEVER, THE EXEC 23 REQUEST MADE BY CLOAD OR COMPL WAS REJECTED BY THE OPERATING SYSTEM. THIS ERROR COULD ONLY HAPPEN IF THE LANGUAGE WAS PURGED FROM THE SYSTEM BETWEEN THE 'RP' AND THE EXEC REQUEST. IF YOU GET THIS ERROR, TRY AGAIN. IF IT HAPPENS AGAIN REPORT IT TO THE SYSTEM MANAGER. "" CL- 07 THIS ERROR MAY OCCUR WHEN THE LANGUAGE REQUESTED IN THE OPTIONAL CONTROL STATEMENT OR THE SOURCE FILE CONTROL STATEMENT WAS RECOGNIZED BUT THE LANGUAGE WAS NOT FOUND. COMPL & CLOAD BOTH TRY TO SCHEDULE THE REQUESTED LANGUAGE, FAILING THAT, THEY BOTH TRY TO ' RP ' THE LANGUAGE. IF THAT FAILS THEN THE LANGUAGE DOES NOT EXIST ON THE SYSTEM. IF THIS ERROR OCCURS FOR A LANGUAGE THUT WAS PREVIOUSLY ON THE SYSTEM, CONTACT THE SYSTEM MANAGER AS THE LANGUAGE HAS BEEN REMOVED FROM THE SYSTEM. "" CL- 08 THE LANGUAGE REQUESTED EXISTS ON THE SYSTEM AND COMPL OR CLOAD WAS IN THE PROCESS OF ' RP 'ING IT. WHEN THE FILE WAS CLOSED AN FMP ERROR OCCURED. THAT ERROR WAS LISTED WITH THE CL- 08 ERROR MESSAGE. "" CL- 09 THE LANGUAGE REQUESTED EXISTS ON THE SYSTEM AND COMPL OR CLOAD WAS IN THE PROCESS OF ' RP ' ING IT. HOWEVER, THAT ' RP ' FAILED BECAUSE THE CHECKSUM CALCULATED WHEN THE LANGUAGE WAS 'SP' ED DID NOT MATCH THE SYSTEM CHECKSUM. GENERALLY THIS ERROR MEANS THAT THE PROGRAM WAS NOT LOADED ON THIS SYSTEM BUT THAT THE ABSOLUTE MEMORY IMAGE OF THE PROGRAM (TYPE 6 FILE) WAS BROUGHT OVER TO THIS SYSTEM VIA A FMGR 'ST' OR 'DU' COMMAND. PROGRAMS TO BE RUN ON THIS SYSTEM MUST BE LOADED ON THIS SYSTEM WITH THE LOADR PROGRAM OR THE GENERATOR. NO OTHER METHOD OF CREATING ABSOLUTE PROGRAMS IS ALLOWED. THE FILE CONTAINING THE LANGUAGE AND ALL ITS SEGMENT FILES SHOULD BE PURGED AND THE PROGRAM LOADED WITH THE LOADR. "" CL- 10 THE LANGUAGE REQUESTED EXISTS ON THE SYSTEM AND COMPL OR CLOAD WAS IN THE PROCESS OF 'RP'ING THE LANGUAGE. HOWEVER, DURING THE OPEN REQUEST AN FMP ERROR OCCURED. TTHIS ERROR WAS REPORTED WITH THE CL- 10 ERROR MESSAGE. "" CL- 11 THIS SESSION HAS MORE THAN 80 SPOOL FILES CURRENTLY RESIDING ON THE SPOOL DISC. CLOAD AND COMPL USE FILE NAMES CONSTRUCTED AS FOLLOWS: CHAR 1 & 1 = CO CHAR 3 & 4 = SESSION # (01 - 99) THIS IS THE NUMBER LISTED IN THE BREAK POINT MODE S = XX COMMAND ? THE XX IS THE USERS SESSION # CHAR 5 & 6 (01 - 80) THIS IS JUST A COUNTER THE FILES WOULD BE CREATED AS COXX01 THEN COXX02 AND SO ON. THESE FILES CONTAIN THE OUT SPOOLED LISTING. THE CL- 11 ERROR MEANS THAT 80 OF THESE FILES ALREADY EXIST AND NO MORE WILL BE CREATED FOR THIS SESSION. NOTE THAT RU,COMPL,SOURCE,6:NS WILL INHIBIT SPOOLING TO LU 6. THAT IS, A ' 6:NS ' IN THE LIST NAMR POSITION WILL INHIBIT SPOOLING AND BYPASS THIS ERROR CONDITION. "" CL- 12 THE COMPILER WAS ABORTED AND THUS THE COMPLILATION WAS NOT SUCCESSFULLY COMPLETED. THE ABNORMAL END WAS PROBABLY DUE TO AN ' OF ' COMMAND. IF THE ABNORMAL END WAS DUE TO OTHER TYPE COMPILER ERRORS THE ERROR WILL BE ON THE LISTING OR REPORTED TO YOUR TERMINAL. TRY THE COMPILATION AGAIN. IF IT FAILS AGAIN CONSULT YOUR SYSTEM MANAGER. "" CL- 13 THE COMPILATION WAS NOT SUCCESSFUL. ERRORS OR WARNINGS WERE FOUND. YOUR BEST BET IS TO GO GET THE LISTING, CORRECT THE ERROR, AND TRY AGAIN. GOOD LUCK ! "" CL- 14 THIS ERROR RESULTS WHEN THE SYSTEM IS OUT OF ID SEGMENTS AND IT IS IMPOSSIBLE TO ' RP ' THE COMPILER OR LOADR. GO GET THE SYSTEM MANAGER AS HE IS THE ONLY ONE WHO WILL KNOW WHICH ID SEGMENTS CAN BE DONE AWAY WITH. AFTER SOME ID SEGMENTS ARE FREE TRY AGAIN AND THE COMPILATION SHOULD WORK. "" CL- 15 THIS ERROR MEANS THAT ONE OF THE INPUT PARAMETERS WAS IN ERROR. MOST OFTEN IT MEANS THAT THE LIST LU THAT YOU SPECIFIED IS ILLEGAL OR NOT DEFINED FOR YOUR SESSION. "" CL- 30 CLOAD WAS TRYING TO ' RP ' THE LOADR BUT ENCOUNTERED AN FMP ERROR ON THE CLOSE OF THE FILE THAT CONTAINED THE LOADR. THE FMP ERROR WAS LISTED WITH THE CL- 30 ERROR. YOU SHOULD REPORT THIS TO THE SYSTEM MANAGER. "" CL- 31 CLOAD WAS TRYING TO ' RP ' THE LOADR AND A CHECKSUM ERROR RESULTED. THIS COULD ONLY OCCUR IF THE LOADR WAS NOT LOADED ON THIS SYSTEM BUT WAS BROUGHT OVER TO THIS SYSTEM VIA A FMGR 'ST' OR 'DU' COMMAND. THIS ERROR IS A SERIOUS ONE AND THE SYSTEM MANAGER SHOULD BE CONSULTED. "" CL- 32 CLOAD WAS TRYING TO ' RP ' THE LOADR BUT ENCOUNTERED AN FMP ERROR ON THE FMP OPEN REQUEST. YOU SHOULD REPORT THIS TO THE SYSTEM MANAGER. "" CL- 33 THIS SHOULD BE AN IMPOSSIBLE ERROR ! THE ONLY WAY THIS COULD HAPPEN IS IF THE LOADR WAS NOT LOADED AT GENERATION TIME OR IF AN ILLEGAL NON SUPPORTED MEMORY OR DISC MODIFICATION HAS BEEN MADE. REPORT THIS TO THE SYSTEM MANAGER IMMEDIATELY ! "" CL- 34 THE LOADR WAS LOADING YOUR PROGRAM BUT WAS ABORTED ABNORMALLY. THIS WAS PROBABLY THE RESULT OF AN ' OF ' COMMAND. ANY OTHER ABNORMAL ENDING ERROR WILL BE REPORTED TO YOUR CONSOLE. TRY THE LOAD AGAIN. IF THE ERROR OCCURS AGAIN REPORT IT TO THE SYSTEM MANAGER. "" CL- 35 THE LOAD WAS NOT SUCCESSFUL. MORE OFTEN THAN NOT LOAD ERRORS ARE A RESULT OF UNDEFINED EXTERNALS. CHECK THE LOADR LISTING FOR THE TYPE OF ERROR. IF IT IS AN UNDEFINED EXTERNAL, THEN YOU ARE PROBABLY MISSING A SUBROUTINE SOMEWHERE. IF THIS IS THE CASE CLOAD IS NOT THE PROGRAM YOU SHOULD BE USING. RATHER, YOU SHOULD BE USING THE PROGRAMS COMPL TO COMPILE YOUR CODE AND THE LOADR TO LOAD THE SEPARATE MODULES THAT THE PROGRAM REQUIRES. "" CL- 36 THIS IS A LOADR SCHEDULING ERROR. FOR SOME REASON THE CLOAD PROGRAM WAS UNABLE TO CREATE A COPY OF THE LOADR FOR YOU AND EVEN THE ORGINAL LOADR WAS NOT AVAILABLE. CALL THE SYSTEM MANAGER FOR ASSISTENCE. "" CL- 37 THE LIST DEVICE FOR CLOAD MUST BE AN LU BECAUSE BOTH THE COMPILER AND THE LOADR MUST TALK TO THE DEVICE. IF THE LOADR WERE TO LIST TO THE SAME FILE THAT THE COMPILER DID THE COMPILER LISTING WOULD BE OVERLAYED. YOU CAN GET THE LISTING TO GO TO A FILE, HOWEVER, IF YOU USE THE SPOOL SYSTEM. (IE THE :SL,LU#,NAMR COMMAND) "" GASP -48 SMP CANNOT BE SCHEDULED SMP PROGRAM IS NOT FOUND OR THERE IS NOT A BIG ENOUGH PARTITION TO RUN SMP. THE DEFAULT FOR SMP IS TYPE 2 (REALTIME) AND 6 PAGES IN SIZE. "" GASP -33 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. "" GASP -32 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. "" GASP -14 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. ""