HELP INFO FILE FOR PROGRAM 92067-18121 "" REV "HELP 92067-18122 REV.2026 800430 RTE-IVB HELP FILE "" FMGR-102 ILLEGAL D.RTR CALL SEQUENCE A LOCK WAS NOT REQUESTED FIRST OR THE FILE WAS NOT OPENED EXCLUSIVELY. POSSIBLY AN OPERATOR ERROR, SUCH AS REMOVING A CARTRIDGE WITHOUT DISMOUNTING IT FIRST. "" FMGR-101 ILLEGAL PARAMETER IN D.RTR CALL POSSIBLY AN OPERATOR ERROR. RECHECK THE PREVIOUS ENTRIES FOR ILLEGAL OR MISPLACED PARAMETERS. THIS ERROR CAN ALSO HAPPEN WHEN A REQUEST IS MADE TO CREATE A SCRATCH FILE AND THAT SCRATCH FILE ALREADY EXISTS. IF D.RTR IS UNABLE TO PURGE THE EXISTING SCRATCH FILE, THIS ERROR IS RETURNED. THIS CAN ONLY HAPPEN IF SOME OTHER PROGRAM HAS THE SCRATCH FILE OPEN. SEE THE SYSTEM MANAGER. "" FMGR-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. "" FMGR-048 SPOOL NOT INITIALIZED OR SMP CANNOT BE SCHEDULED IF SPOOLING NOT INITIALIZED RUN GASP TO DO SO. OTHERWISE, 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. "" FMGR-047 NO SESSION LU AVAILABLE FOR SPOOL FILE IF THE SESSION LU TO BE USED FOR THE SPOOL FILE IS NOT SPECIFIED DURING SET UP, SMP ALLOCATES A SESSION LU LESS THAN 64 THAT IS NOT ALREADY USED IN THE SESSION SWITCH TABLE. USE :SL,LU,- COMMAND TO RELEASE A SESSION LU IN THE SPARE PART OF THE SESSION SWITCH TABLE. "" FMGR-046 GREATER THAN 255 EXTENTS ATTEMPT TO CREATE EXTENT 256. MAKE FILE SIZE OF MAIN LARGER. IF GENERATED DURING A SM COMMAND, THE MESSAGE IS NOT PUT IN THE MESSAGE FILE. IT IS TRUNCATED AT THE LAST VALID MESSAGE. "" FMGR-041 NO ROOM IN SST THERE ARE NO SPARE ENTRIES LEFT IN THE SESSION SWITCH TABLE. SPARE ENTRIES CAN BE RECOVERED BY USING THE :SL,LU,- COMMAND, WHERE LU IS A SESSION LOGICAL UNIT NUMBER THAT IS NOT NEEDED. "" FMGR-040 LU NOT FOUND IN SST TRYING TO ACCESS AN LU THAT IS NOT IN YOUR SESSION SWITCH TABLE. USE THE SL COMMAND TO ADD THE LU TO THE SST. "" FMGR-039 SPOOL LU NOT MAPPED TO THE SPOOL DRIVER SPOOL LU MUST POINT TO A SPOOL EQT. SWITCH ALL SPOOL LU'S TO POINT TO SPOOL EQT'S AND TRY THE SPOOL FILE SET UP AGAIN. "" FMGR-038 ILLEGAL SCRATCH FILE NUMBER ATTEMPT TO CREATE A SCRATCH FILE WILL AN ILLEGAL SCRATCH FILE NUMBER. THE RANGE FOR SCRATCH FILE NUMBERS IS 0 THROUGH 99. ISSUE CREATE AGAIN WITH A NUMBER IN THE CORRECT RANGE. "" FMGR-036 LOCK ERROR ON DEVICE A CALL TO OPENF CAUSED AN ATTEMPTED LOCK ON A DEVICE AND THAT LOCK WAS UNSUCCESSFUL. THIS COULD HAPPEN IF THE DEVICE IS ALREADY LOCKED OR IF THERE ARE NO RESOURCE NUMBERS AVAILABLE. "" FMGR-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. "" FMGR-034 DISC ALREADY MOUNTED. AN ATTEMPT WAS MADE TO MOUNT A DISC THAT IS ALREADY MOUNTED IN THE CARTRIDGE DIRECTORY. EITHER DISMOUNT THE DUPLICATE DISC OR MOUNT A DIFFERENT ONE. "" FMGR-033 NOT ENOUGH ROOM ON CARTRIDGE AN ATTEMPT WAS MADE TO ACCESS A CARTRIDGE WHICH DOES NOT HAVE ENOUGH ROOM. TRY USING ANOTHER CARTRIDGE OR DECREASE THE FILE SIZE. "" FMGR-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. "" FMGR-030 VALUE TOO LARGE FOR PARAMETER 1. THE VALUE SUPPLIED IN THE PARAMETER IS BEYOND THE DEFINED RANGE. 2. THIS ERROR CAN BE GENERATED WHEN A PARAMETER IS SUPPLIED FOR THE PURPOSE OF GETTING RETURN INFORMATION FROM A ROUTINE. IF THE PARAMETER SUPPLIED IS A SINGLE WORD BUT THE VALUE OF THE INFOR- MATION TO BE RETURNED IS A DOUBLE WORD, THE ERROR WILL BE GENERATED. "" FMGR-026 QUEUE FULL OR MAX PENDING SPOOLS EXCEEDED THE SPOOL QUEUE IS FULL OR THE MAXIMUM NUMBER OF SPOOLS PENDING HAS BEEN EXCEEDED. THE JOB MUST BE RE-RUN WHEN THE SPACE BECOMES AVAILABLE. "" FMGR-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. "" FMGR-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. "" FMGR-023 NO AVAILABLE SPOOL FILES ALL SPOOL FILES ARE CURRENTLY BEING USED. RE-RUN THE JOB AFTER A SPOOL FILE BECOMES AVAILABLE. "" FMGR-022 NO AVAILABLE SPOOL LU'S ALL SPOOL LOGICAL UNITS ARE CURRENTLY UNAVAILABLE. RE-RUN THE JOB AFTER A SPOOL LU BECOMES AVAILABLE. "" FMGR-021 ILLEGAL DESTINATION LU THE LU SPECIFIED WAS NOT ALLOCATED BY GASP. TRY AGAIN USING A LU ALLOCATED BY GASP. "" FMGR-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. "" FMGR-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. "" FMGR-018 ILLEGAL LU ATTEMPT TO ACCESS AN LU THAT IS (1) NOT ASSIGNED TO THE SYSTEM, OR (2) IS NOT DEFINED IN THE USER'S SESSION SWITCH TABLE (SST). "" FMGR-017 ILLEGAL READ/WRITE ON TYPE 0 FILE 1. AN ATTEMPT WAS MADE TO READ, WRITE, OR POSITION A TYPE 0 FILE THAT DOES NOT SUPPORT THE OPERATION. THIS ERROR MAY ALSO OCCUR ON AN ATTEMPT TO PERFORM SUCH AN OPERATION ON A SPOOL FILE WHICH DOES NOT SUPPORT THE OPERATION (E.G., AN ATTEMPTED WRITE ON A READ- ONLY SPOOL FILE). CHECK THE FILE PARAMETERS OR THE NAMR. 2. WRITING TO A SPOOL FILE AND THERE IS NO MORE ROOM ON CARTRIDGE. "" FMGR-016 ILLEGAL TYPE 0 OR SIZE=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. CHECK THE SIZE AND TYPE PARAMETERS. "" FMGR-015 ILLEGAL NAME THE FILE NAME DOES NOT CONFORM TO THE SYNTAX RULES. CORRECT THE NAME AND RE-ENTER THE COMMAND. "" FMGR-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. "" FMGR-013 DISC LOCKED THE CARTRIDGE SPECIFIED IS LOCKED. INITIALIZE THE CARTRIDGE IF IT WAS NOT INITIALIZED, OTHERWISE KEEP TRYING. "" FMGR-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 DEPEND ON THE FILE TYPE AND THE CALL. "" FMGR-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. "" FMGR-010 NOT ENOUGH PARAMETERS ONE OR MORE OF THE REQUIRED PARAMETERS WERE OMITTED FROM THE CALL. ENTER THE REQUIRED PARAMETERS. "" FMGR-009 ATTEMPT TO USE APOSN OR FORCE TO 1 A TYPE 0 FILE A TYPE 0 FILE CANNOT BE POSITIONED WITH APOSN OR BE FORCED TO A TYPE 1 FILE. CHECK THE FILE TYPE. "" FMGR-008 FILE OPEN OR LOCK REJECTED AN ATTEMPT WAS MADE TO OPEN A FILE THAT WAS ALREADY OPENED EXCLUSIVELY OR WAS ALREADY OPENED TO SEVEN PROGRAMS, OR THE CARTRIDGE CONTAINING THE FILE IS LOCKED. USE THE CL OR DL COMMAND TO LOCATE THE LOCK. IF THE CARTRIDGE IS BEING PACKED, CHECK TO SEE IF SPOOLING IS SHUT DOWN. "" FMGR-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. "" FMGR-006 FILE NOT FOUND AN ATTEMPT WAS MADE TO ACCESS A FILE THAT CANNOT BE FOUND. CHECK THE FILE NAME OR THE CARTRIDGE REFERENCE. "" FMGR-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. "" FMGR-004 RECORD SIZE OF TYPE 2 FILE IS 0 OR UNDEFINED AN ATTEMPT WAS MADE TO CREATE A TYPE 2 FILE WITHOUT SPECIFING THE RECORD SIZE OR SPECIFYING IT TO BE 0. CHECK THE SIZE PARAMETER. "" FMGR-003 BACKSPACE ILLEGAL AN ATTEMPT WAS MADE TO BACKSPACE A DEVICE (OR TYPE 0 FILE) THAT CANNOT BE BACKSPACED. CHECK THE DEVICE TYPE. "" FMGR-002 DUPLICATE FILE NAME A FILE ALREADY EXISTS WITH THE NAME SPECIFIED. REPEAT THE COMMAND WITH A NEW NAME OR PURGE THE EXISTING FILE. "" FMGR-001 DISC ERROR THE DISC IS DOWN. TRY AGAIN AND THEN REPORT THE PROBLEM TO THE SYSTEM MANAGER. "" FMGR 000 BREAK THIS IS AN INFORMATIVE MESSAGE ONLY. NO ERROR HAS OCCURRED. "" FMGR 001 DISC ERROR - LU REPORTED THE DISC ASSOCIATED WITH THE LU REPORTED IS DOWN. REPORT THE PROBLEM TO THE SYSTEM MANAGER. EXAMPLE: FMGR 001 THIS 2-LINE MESSAGE INDICATES A DISC ERROR FMGR 034 HAS BEEN DETECTED ON DISC LU 34. "" FMGR 002 INITIALIZE LU 2! THIS ERROR INDICATES A REQUEST FOR THE USER TO INITIALIZE THE SYSTEM DISC (LU 2) BY ASSIGNING SPECIFIC SYSTEM TRACKS TO FMGR. BEFORE IT IS INITIALIZED, FMGR OBTAINS ALL THE AVAILABLE TRACKS ON THE SYSTEM AND AUXILIARY DISCS AND ASSIGNS THEM TO ITSELF. AFTER IT IS INITIALIZED, FMGR OWNS ONLY THOSE TRACKS SPECIFICALLY ASSIGNED TO IT. THEREAFTER, EACH TIME THE SYSTEM IS LOADED FROM DISC (BOOTED UP), IT RECOVERS THESE TRACKS AUTOMATICALLY AND NO FURTHER INITIALIZATION IS REQUIRED. TO INITIALIZE THE SYSTEM DISC, USE THE FMGR INITIALIZE (IN) COMMAND. EXAMPLE: IN,SC,-2,2,SYS,100 THIS COMMAND WOULD INITIALIZE LU 2, SETTING THE MASTER SECURITY CODE TO "SC", THE CRN TO 2, THE ASCII LABEL TO "SYS" AND THE STARTING FMP DISC TRACK TO 100. THE STARTING FMP TRACK MUST BE AT LEAST 8 TRACKS GREATER THAN THE LAST TRACK USED BY THE SYSTEM. (SYSTEM SIZE IS REPORTED AT THE END OF SYSTEM GENERATION.) "" FMGR 003 INITIALIZE LU 3! THIS ERROR INDICATES A REQUEST FOR THE USER TO INITIALIZE THE AUXILIARY DISC (LU 3) BY ASSIGNING SPECIFIC SYSTEM TRACKS TO FMGR. BEFORE IT IS INITIALIZED, FMGR OBTAINS ALL THE AVAILABLE TRACKS ON THE SYSTEM AND AUXILIARY DISCS AND ASSIGNS THEM TO ITSELF. AFTER IT IS INITIALIZED, FMGR OWNS ONLY THOSE TRACKS SPECIFICALLY ASSIGNED TO IT. THEREAFTER, EACH TIME THE SYSTEM IS LOADED FROM DISC (BOOTED UP), FMGR RECOVERS THESE TRACKS AUTOMATICALLY AND NO FURTHER INITIALIZATION IS REQUIRED. TO INITIALIZE THE AUXILIARY DISC, USE THE FMGR INITIALIZE (IN) COMMAND. EXAMPLE: IN,SC,-3,3,AUX,70 THIS COMMAND WOULD INITIALIZE LU 3, SETTING THE CRN TO 3, THE ASCII LABEL TO "AUX" AND THE STARTING FMP DISC TRACK TO 70. IF AUXILIARY DISC TRACKS ARE NOT TO BE ASSIGNED TO FMGR, THE INITIALIZE COMMAND SHOULD STILL BE SPECIFIED IN RESPONSE TO FMGR 003, BUT THE CARTRIDGE REFERENCE NUMBER SHOULD BE SPECIFIED AS 0. "" FMGR 004 ILLEGAL RESPONSE TO FMGR 002 OR FMGR 003 A COMMAND OTHER THAN AN INITIALIZE COMMAND WAS ENTERED IN RESPONSE TO EITHER A FMGR 002 OR FMGR 003 ERROR. ENTER THE APPROPRIATE INITIALIZE COMMAND. "" FMGR 005 REQUIRED TRACK NOT AVAILABLE - RELATIVE TAT POSITION REPORTED THE FIRST TRACK SPECIFIED IN THE INITIALIZE COMMAND IS NOT AVAILABLE. NOTE THAT THE STARTING TRACK MUST BE AT LEAST 8 TRACKS GREATER THAN THE LAST TRACK USED BY THE SYSTEM. RE-ENTER THE INITIALIZE COMMAND WITH THE FIRST AVAILABLE TRACK REPORTED IN THIS MESSAGE. "" FMGR 006 FMGR SUSPENDED THE FILE MANAGER SUSPENDED ITSELF. READY THE DOWN DEVICE AND ENTER 'GO,FMGR'. "" FMGR 007 CHECKSUM ERROR A CHECKSUM ERROR OCCURRED WHEN READING A PAPER TAPE OR THE FILE BEING READ IS NOT BINARY (TYPE 5 OR 7). CHECK THE FILE TYPE. "" FMGR 008 D.RTR NOT LOADED THE PROGRAM D.RTR WAS NOT FOUND IN THE SYSTEM. LOAD D.RTR AS A PERMANENT PROGRAM. "" FMGR 009 ID SEGMENT NOT FOUND AN RP COMMAND WAS USED TO DEALLOCATE OR REASSIGN THE ID SEGMENT TO THE PROGRAM BEING RESTORED. THE SYSTEM LOOKS FOR A BLANK ID SEGMENT. "" FMGR 010 INPUT ERROR A SYNTAX ERROR IN THE STATEMENT OCCURRED. LOOK FOR A MISSING COLON (BATCH INPUT) OR EXTRA COLON (INTERACTIVE INPUT), AN UNDEFINED COMMAND, AN ERROR IN THE NAMR SUBPARAMETERS, A COMMAND THAT IS TOO LONG, ETC. RE-ENTER THE COMMAND. IF RECEIVED AFTER ENTERING AN ABORT COMMAND, THERE WERE NO ACTIVE JOBS. "" FMGR 011 DO 'OF,XXXXX,8' ON NAMED PROGRAMS AN ATTEMPT WAS MADE TO PACK A DISC TO WHICH THE NAMED PROGRAMS ARE STILL ALLOCATED. ENTER EITHER 'RP,NAMR,PROGRAM' OR 'OF,PROGRAM,8' TO REMOVE THE NAMED PROGRAMS. "" FMGR 012 DUPLICATE DISC LABEL OR LU AN ATTEMPT WAS MADE TO MOUNT A CARTRIDGE THE SAME LABEL OR LOGICAL UNIT NUMBER OF A CARTRIDGE THAT IS ALREADY MOUNTED. RE-ENTER THE THE COMMAND WITH ANOTHER LABEL OR LU, OR DISMOUNT THE DUPLICATE CARTRIDGE. THE ERROR MAY ALSO OCCUR IF THE USER DISMOUNTS A PRIVATE CARTRIDGE FROM HIS SESSION AND ATTEMPTS TO RE-MOUNT IT AS A GROUP CARTRIDGE, OR CONVERSELY, IF HE DISMOUNTS A GROUP CARTRIDGE FROM HIS SESSION AND ATTEMPTS TO RE-MOUNT IT AS A PRIVATE CARTRIDGE (DEFAULT). "" FMGR 013 TR STACK OVERFLOW MORE THAN 10 NESTED TR COMMANDS HAVE BEEN USED. "" FMGR 014 REQUIRED ID SEGMENT NOT FOUND AN ID SEGMENT CANNOT BE FOUND FOR THE SPECIFIED PROGRAM. CHECK THE PROGRAM NAME OR LOAD THE PROGRAM. A BLANK ID SEGMENT CANNOT BE FOUND FOR A PROGRAM BEING RESTORED. ENTER AN 'OF' COMMAND TO RELEASE AN ID SEGMENT. "" FMGR 015 LS TRACK REPORT THIS IS AN INFORMATIVE MESSAGE TO REPORT THE LOGICAL UNIT NUMBER AND TRACK OF THE CURRENT LS AREA. "" FMGR 016 INSUFFICIENT SYSTEM TRACKS FOR RP AN ATTEMPT WAS MADE TO RESTORE A PROGRAM FILE THAT IS NOT ON THE SYSTEM OR AUXILIARY DISC AND THERE IS INSUFFICIENT SPACE IN THE SYSTEM TRACK POOL TO COPY THE PROGRAM. EITHER WAIT UNTIL MORE TRACK POOL SPACE BECOMES AVAILABLE, OR MOVE THE FILE TO LU 2 OR LU 3, AND THEN RE-ENTER THE COMMAND. "" FMGR 017 ID SEGMENT NOT SET UP BY RP IN ORDER FOR AN ID SEGMENT TO BE RELEASED BY A 'RP' COMMAND, IT MUST HAVE BEEN SET UP BY A 'RP' COMMAND. TRY USING 'OF,PROGRAM' TO RELEASE THE SPECIFIED PROGRAM. "" FMGR 018 PROGRAM NOT DORMANT AN 'RP,NAMR,PROGRAM' COMMAND WAS ATTEMPTED WHEN THE PROGRAM IS ACTIVE. ENTER 'OF,PROGRAM' AND THEN REPEAT THE 'RP' COMMAND. "" FMGR 019 FILE NOT SET UP BY SP ON CURRENT SYSTEM THE PROGRAM FILE BEING RESTORED HAD A PARITY ERROR, WAS NOT SET UP CORRECTLY, OR WAS NOT SET UP BY A 'SP' COMMAND IN THE CURRENT SYSTEM. RELOAD THE PROGRAM AND TRY AGAIN. "" FMGR 020 ILLEGAL TYPE 0 FILE AN ATTEMPT WAS MADE TO CREATE A TYPE 0 FILE ON A LOGICAL UNIT THAT IS NOT ASSIGNED IN THE SYSTEM. RE-ENTER THE COMMAND USING ANOTHER LOGICAL UNIT. "" FMGR 021 ILLEGAL DISC SPECIFIED AN ATTEMPT WAS MADE TO COPY FILES TO OR FROM THE SAME DISC OR A DISC THAT IS NOT MOUNTED. MOUNT ANOTHER DISC OR USE ANOTHER ALREADY MOUNTED. "" FMGR 022 COPY TERMINATED COPY HAS BEEN TERMINATED AS A RESULT OF COPY ERROR. CHECK THE PARAMETERS AND THE SPECIFIED DISCS. "" FMGR 023 DUPLICATE PROGRAM NAME THE PROGRAM BEING RESTORED IS ALREADY DEFINED IN THE SYSTEM. CHANGE THE NAME OF THE PROGRAM, ENTER 'OF,PROGRAM', OR RELEASE THE ID SEGMENT. "" FMGR 041 PROGRAM CANNOT BE A SEGMENT THE PROGRAM SPECIFIED IS A PROGRAM SEGMENT (TYPE 5). LS TRACKS CANNOT BE ASSIGNED TO A PROGRAM SEGMENT. ORDINARILY, THE LS TRACKS ARE ASSIGNED TO THE PROGRAM EDITR WHEN MS IS EXECUTED. IF THE LS TRACKS ARE TO BE ASSIGNED TO A DIFFERENT PROGRAM, SPECIFY THIS PROGRAM'S NAME. "" FMGR 042 LU CANNOT BE SWITCHED AN ATTEMPT WAS MADE TO SWITCH A LOGICAL UNIT WHICH CANNOT BE SWITCHED. IF A DISC LU, THE SESSION LU MUST BE THE SAME AS THE SYSTEM LU. SESSION LU 1 CANNOT BE SWITCHED. "" FMGR 043 LU NOT FOUND IN SST AN ATTEMPT WAS MADE TO ACCESS A LOGICAL UNIT THAT IS NOT DEFINED IN THE USER'S SESSION SWITCH TABLE. USE THE SL COMMAND TO ADD THE LU TO THE SST. "" FMGR 044 NO MESSAGES WAITING CALLER ISSUED A ME COMMAND BUT THERE WERE NO MESSAGES WAITING TO BE READ. "" FMGR 045 SESSION COMMAND ONLY THE SPECIFIED COMMAND OPERATES ONLY IN THE SESSION ENVIRONMENT. "" FMGR 046 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. THE USER'S CAPABILITY LEVEL CAN BE DISPLAYED USING THE FMGR COMMAND :DP,9P. TO INCREASE YOUR COMMAND CAPABILITY LEVEL, SEE THE SYSTEM MANAGER. "" FMGR 047 SPOOL SET UP FAILED THERE ARE NO AVAILABLE SPOOL FILES OR LOGICAL UNITS, OR THE LOGICAL UNIT TABLE IS FULL. YOU CAN TRY RUNNING THE JOB AGAIN, BUT IF THE ERROR IS FROM A LACK OF SPOOL LOGICAL UNITS OR THE LOGICAL UNIT TABLE BEING FULL YOU MUST RECONFIGURE. "" FMGR 048 GLOBAL SET OUT OF RANGE A GLOBAL WAS SPECIFIED OUT OF THE RANGE OF THE GLOBALS. CHECK THE PARAMETERS AND RE-ENTER THE COMMAND CORRECTLY. "" FMGR 049 CAN'T RUN RP'ED PROGRAM THE PROGRAM RESTORED FROM THE FILE DOES NOT EXECUTE. USUALLY THIS IS CAUSE BY ATTEMPTING TO RUN A SEGMENT OF THE SPECIFIED PROGRAM. CHECK THE PROGRAM. "" FMGR 050 NOT ENOUGH PARAMETERS LESS THAN THE REQUIRED NUMBER OF PARAMETERS WERE SPECIFIED. RE-ENTER COMMAND CORRECTLY. "" FMGR 051 ILLEGAL MASTER SECURITY CODE AN ATTEMPT WAS MADE TO RE-INITIALIZE A CARTRIDGE OR LIST FILES WITH AN INCORRECT MASTER SECURITY CODE. RE-ENTER THE COMMAND WITH THE CORRECT CODE. "" FMGR 052 ILLEGAL LU 1. AN ATTEMPT WAS MADE TO SWITCH A SESSION LU TO A SYSTEM LU WHICH IS A DISC, BUT THE SESSION LU NUMBER DOES NOT EQUAL THE SYSTEM LU NUMBER. (FOR DISCS, THE MAPPING FROM SESSION LU TO SYSTEM LU MUST BE DIRECT.) OR 2. ILLEGAL LU(S) SPECIFIED IN THE SL COMMAND. CHECK THAT THE LU IS POSITIVE AND LESS THAN THE LARGEST LU DEFINED IN THE SYSTEM, AND THAT THE SESSION LU IS LESS THAN 64. OR 3. AN ATTEMPT WAS MADE TO INITIALIZE THE FILE MANAGER USING A LOGICAL UNIT OTHER THAN LU 2 OR 3. THE RESPONSE TO THE FMGR 002 MESSAGE MUST BE A COMMAND TO INITIALIZE LU 2. THE RESPONSE TO THE FMGR 003 MESSAGE MUST BE A COMMAND TO INITIALIZE LU 3. "" FMGR 053 ILLEGAL LABEL OR ILABEL THE SPECIFIED CARTRIDGE REFERENCE NUMBER OR CARTRIDGE ID IS ILLEGAL. THE CARTRIDGE REFERENCE NUMBER MUST BE A POSITIVE NON-ZERO INTEGER AND THE CARTRIDGE ID MUST BE A LEGAL FILE NAME. "" FMGR 054 DISC NOT MOUNTED AN ATTEMPT WAS MADE TO DISMOUNT OR REFERENCE A DISC CARTRIDGE NOT MOUNTED TO THE CALLER. TO REFERENCE IT, MOUNT THE DISC CARTRIDGE USING THE "MC" COMMAND. IF UNDER SESSION CONTROL, THE "AC" COMMAND COULD BE USED INSTEAD TO ALLOCATE DISC SPACE WITH THE SPECIFIED CRN. THIS ERROR ALSO OCCURS IF AN ATTEMPT IS MADE BY A SESSION USER (NOT THE SYSTEM MANAGER) TO DISMOUNT A SYSTEM DISC. A SESSION USER IS ALLOWED ACCESS TO A SYSTEM DISC EVEN THOUGH IT DOES NOT REALLY BELONG TO HIM, I.E. HE HAS NO CONTROL OVER THE MOUNTING OR THE DISMOUNTING OF IT. "" FMGR 055 MISSING PARAMETER A REQUIRED PARAMETER HAS BEEN OMITTED. CHECK THE COMMAND AND RE-ENTER IT WITH THE MISSING PARAMETER. "" FMGR 056 BAD PARAMETER A PARAMETER WAS SPECIFIED INCORRECTLY OR A TRACK PARAMETER SPECIFIES A TRACK THAT IS OUTSIDE THE RANGE OF THE FMGR TRACKS. CHECK THE COMMAND AND RE-ENTER IT CORRECTLY. "" FMGR 057 BAD TRACK NOT IN FILE AREA THE SPECIFIED TRACK IS IN THE SYSTEM AREA OR IS A DIRECTORY TRACK. CORRECT THE COMMAND AND RE-ENTER IT. "" FMGR 058 LG AREA EMPTY AN ATTEMPT WAS MADE TO SAVE THE CONTENTS OF THE LG AREA WHICH IS EMPTY. USE THE MR COMMAND TO MOVE A FILE TO THE LG AREA. "" FMGR 059 REPORTED TRACK UNAVAILABLE A RE-INITIALIZATION ATTEMPT WILL LOWER THE FIRST TRACK INTO THE SYSTEM AREA. THE LAST TRACK IS REPORTED. RE-ENTER THE COMMAND WITH THE FIRST TRACK SPECIFIED AS THE LAST TRACK + 8 (THE MINIMUM). "" FMGR 060 DO YOU REALLY WANT TO PURGE THIS DISC? A RE-INITIALIZATION ATTEMPT WILL RAISE THE FIRST TRACK OR LOWER THE DIRECTORY TRACKS INTO THE FILE AREA AND DESTROY A FILE. ENTER '??' OR 'NO' TO STOP THE REINITIALIZATION. ENTER 'YES' TO CONTINUE. "" FMGR 061 DO A "DC" AND A "MC" ON THIS CR AN ATTEMPT WAS MADE TO REPLACE A MOUNTED CARTRIDGE WITH AN CARTRIDGE THAT HAS NOT BEEN PREVIOUSLY INITIALIZED WITHOUT ENTERING A 'DC' AND A 'MC' COMMAND. ENTER A 'DC' AND 'MC' COMMAND FOR THIS CARTRIDGE. NOTE: BE SURE TO DO A DC SPECIFING THE RELEASE RESOURCES "RR" OPTION. "" FMGR 062 MORE THAN 63 DISCS AN ATTEMPT WAS MADE TO MOUNT THE 64TH CARTRIDGE (THE LIMIT IS 63 CARTRIDGES). DISMOUNT A CARTRIDGE TO MAKE ROOM, IF POSSIBLE. "" FMGR 063 EXCEEDING SESSION DISC LIMIT AN ATTEMPT IS BEING MADE TO MOUNT MORE DISCS TO A SESSION THAN IS ALLOWED IN THE USER'S ACCOUNT. DISMOUNT AN UNUSED DISC AND RE-ENTER THE COMMAND. TO INCREASE YOUR ACCOUNT'S DISC LIMIT, CONSULT THE SYSTEM MANAGER. "" FMGR 064 NO DISC AVAILABLE FROM DISC POOL ALL DISCS IN DISC POOL ARE ALLOCATED OR THERE ARE NO DISCS AVAILABLE THAT ARE BIG ENOUGH. THIS ERROR CAN ALSO OCCUR IF # DIRECTORY TRACKS SPECIFIED IS TOO LARGE. #DIRECTORY TRACKS SPECIFIED MUST BE A REASONABLE NUMBER IN RELATIONSHIP TO THE TOTAL NUMBER OF TRACKS ON THE DISC. IF DISC SPACE IS BEING ALLOCATED FROM THE DISC POOL AND SIZE WAS NOT SPECIFIED (I.E. FIRST FREE DISC IS ALLOCATED), THE MOUNT ROUTINE WILL CONTINUE TO SEARCH THE DISC POOL UNTIL A DISC IS FOUND THAT WIL PASS THE "REASONABLE" TEST. IN THIS CASE, IT IS POSSIBLE THAT EVEN THOUGH THERE ARE FREE DISCS IN THE POOL, NONE WILL BE ALLOCATED BECAUSE # DIRECTORY TRACKS WAS SO LARGE. "" FMGR 065 CONFLICT IN SST DEFINITION THE SPECIFIED LU NUMBER IS ALREADY DEFINED AS A SESSION LU IN THE USER'S SESSION SWITCH TABLE (SST). THIS WILL OCCUR IF THE USER HAS SPECIFIED A DISC LU NUMBER IN THE MOUNT COMMAND, BUT THIS NUMBER IS ALREADY DEFINED IN THE SST. IF IT IS NECESSARY TO MOUNT THIS DISC LU, CHANGE THE CONFLICTING ENTRY IN THE SST. THIS CAN BE DONE BY USING THE SL COMMAND TO REMOVE THE SST ENTRY WITH THE CONFLICTING SESSION LU AND, IF DESIRED, RE-ENTERING IT IN THE SWITCH TABLE WITH A DIFFERENT SESSION LU NUMBER. "" FMGR 066 NO ROOM IN SST THERE ARE NO SPARE ENTRIES LEFT IN THE SESSION SWITCH TABLE. SPARE ENTRIES CAN BE RECOVERED BY USING THE :SL,LU,- COMMAND, WHERE LU IS A SESSION LOGICAL UNIT NUMBER THAT IS NOT NEEDED. "" FMGR 067 PROGRAM NOT FOUND THE PROGRAM TO BE EXECUTED WAS NOT FOUND AMONG THE SYSTEM ID SEGMENTS, NOR WAS IT FOUND AS A TYPE 6 FILE ON A SYSTEM DISC. CHECK THE PROGRAM NAME SPECIFIED FOR CORRECTNESS OR RELOAD THE PROGRAM. ON A HE (HELP) COMMAND, THE FMGR 067 ERROR INDICATES THE PROGRAM HELP COULD NOT BE FOUND. ON A WH (WHZAT) COMMAND, THE ERROR INDICATES THE PROGRAM WHZAT COULD NOT BE FOUND. "" FMGR 068 LU NOT IN VARIABLE PART OF SST ONLY LU'S IN THE VARIABLE PART OF THE SESSION SWITCH TABLE (SST) MAY BE DELETED. "" FMGR 069 JOB LOGON FAILED THE JOB ACCOUNT COULD NOT BE LOGGED ON. THE REASON FOR THE FAILURE IS PRINTED ON THE SYSTEM CONSOLE. "" FMGR 070 SECTORS/TRACK VALUE TOO LARGE THE SECTORS PER TRACK VALUE SPECIFIED IN THE INITIALIZE COMMAND IS LARGER THAN THE ACTUAL SECTORS PER TRACK VALUE FOR THE DISC. LET THE SECTORS PER TRACK PARAMETER DEFAULT TO THE ACTUAL SECTORS PER TRACK VALUE FOR THE DISC, OR SPECIFY A SMALLER VALUE. "" FMGR 071 DO "EX,SP" TO SAVE OR "EX,RP" TO RELEASE PRIVATE CARTRIDGES AN ATTEMPT WAS MADE TO LOG-OFF WITH A PRIVATE DISC(S) STILL MOUNTED TO THE USER'S SESSION. SPECIFYING "EX,RP" WILL RELEASE THE USER'S PRIVATE DISC(S); IF THE DISC WAS ALLOCATED FROM THE DISC POOL, IT IS RETURNED TO THE POOL FOR POSSIBLE RE-ALLOCATION TO ANOTHER USER. IF "EX,SP" IS SPECIFIED, THE USER'S PRIVATE DISC(S) WILL REMAIN MOUNTED TO THIS USER; ON THE NEXT LOG-ON BY THIS USER, THE DISC(S) WILL BE MOUNTED TO THE NEW SESSION. NOTE THAT GROUP DISCS ARE, BY DEFAULT, LEFT MOUNTED AT LOG-OFF. TO RELEASE GROUP DISCS AT LOG-OFF, SPECIFY "EX,,RG". "" FMGR 072 LU NOT INTERACTIVE THE LOGICAL UNIT SPECIFIED IN A CT COMMAND MUST REFER TO AN INTERACTIVE DEVICE. "" FMGR 073 ACCOUNT NOT FOUND AN ATTEMPT WAS MADE TO SEND A MESSAGE TO A USER FOR WHOM AN ACCOUNT DOES NOT EXIST. CHECK THE USER.GROUP NAME OR THE ORDER OF THE PARAMETERS IN THE SM COMMAND FOR CORRECTNESS. "" FMGR 074 JO COMMAND EXPECTED THE FIRST COMMAND IN A JOB MUST BE, AND WAS NOT, A JO COMMAND. "" FMGR 075 CAN'T RESTORE TYPE 6 PGM (USER PROTECTED) THE SPECIFIED PROGRAM IS SAVED AS A TYPE 6 FILE WITH USER PROTECTION ("SP,PROG,PR"). IT CAN ONLY BE RUN OR RP'ED FROM THE TYPE 6 FILE BY THE USER WHO ISSUED THE SP COMMAND, OR BY USERS WHO ARE LINKED TO THE ACCOUNT OF THE USER WHO ISSUED THE SP COMMAND. "" FMGR 076 CAN'T RESTORE TYPE 6 PGM (GROUP PROTECTED) THE SPECIFIED PROGRAM IS SAVED AS A TYPE 6 FILE WITH GROUP PROTECTION ("SP,PROG,GR"). IT CAN ONLY BE RUN OR RP'ED FROM THE TYPE 6 FILE BY USERS BELONGING TO THE SAME GROUP AS THE USER WHO ISSUED THE SP COMMAND. "" FMGR 077 CAN'T RESTORE TYPE 6 PGM (INSUFFICIENT CAPABILITY) THE SPECIFIED PROGRAM IS SAVED AS A TYPE 6 FILE WITH CAPABILITY LEVEL PROTECTION ("SP,PROG,,CAP", WHERE CAP IS THE MINIMUM CAPABILITY LEVEL REQUIRED TO RUN OR RP THE PROGRAM). THE PROGRAM CAN ONLY BE RUN OR RP'ED FROM THE TYPE 6 FILE BY USERS POSSESSING A CAPABILITY LEVEL GREATER THAN OR EQUAL TO THE LEVEL SPECIFIED WHEN THE PROGRAM WAS SP'ED. FOR EXAMPLE, THE COMMAND "SP,PROG,,50" WILL SAVE PROGRAM "PROG" AND ONLY USERS WITH A CAPABILITY LEVEL OF 50 OR GREATER WILL BE ALLOWED TO RUN OR RP THE PROGRAM FROM THE TYPE 6 FILE. NOTE THAT COMMAND CAPABILITY CHECKING IS STILL IN EFFECT. (THE USER STILL MUST HAVE SUFFICIENT CAPABILITY TO INVOKE THE RU OR RP COMMAND, REGARDLESS OF THE CAPABILITY LEVEL SPECIFIED IN THE SP COMMAND.) "" FMGR 078 CAN'T RESTORE TYPE 6 PGM (INTERNAL ERROR) INTERNAL CONSISTENCY CHECKS HAVE FAILED WHILE ATTEMPTING TO RESTORE A PROGRAM FILE. "" FMGR 079 WARNING - RECORDS TRUNCATED TO 128 WORDS IN A TYPE 2 FILE, RECORDS WHICH ARE LONGER THAN 128 WORDS HAVE BEEN TRUNCATED TO 128 WORDS. "" READ 001 THE REQUESTED MAG TAPE UNIT IS DOWN. USE THE "UP" COMMAND (SPECIFYING THE APPROPRIATE EQT) TO ENABLE THE DEVICE. "" READ 002 THE MAG TAPE READT IS TRYING TO RESTORE CONTAINS INFORMATION IN A FORMAT NOT RESTORABLE BY READT. THE TAPE MAY HAVE BEEN SAVED WITH ANOTHER UTILITY, OR IT MAY HAVE BEEN CONSTRUCTED THROUGH THE FMGR'S "DU" OR "ST" COMMANDS. IN ANY CASE READT CANNOT RESTORE THE DATA. THIS ERROR WILL ALSO RESULT WHEN THE NEXT TAPE OF A TWO OR MORE TAPE CARTRIDGE IS NOT THE CORRECT ONE. MOUNT THE CORRECT TAPE AND DO AS THE UTILITY SUGGESTS. "" READ 003 THE MAG TAPE UNIT 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. "" READ 004 THE PARAMETER DESCRIBING THE DESIRED MAG TAPE UNIT DOES NOT SATISFY READT'S REQUIREMENTS FOR A LEGAL MAG TAPE LU. 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. "" READ 005 THE DESIRED MAG TAPE UNIT IS OFF-LINE. THE ON-LINE BUTTON MUST BE DEPRESSED TO ENABLE THE ON-LINE SWITCH. "" READ 006 READT REJECTED THE USE OF THE SPECIFED DISC LU. THERE ARE A VARIETY OF REASONS FOR THIS, THEY INCLUDED: 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. "" READ 007 THE DRIVER DETECTED A PARITY ERROR WHEN READING FROM THE MAG TAPE. IF THIS HAPPENS AGAIN THE TAPE MAY BE IRRECOVERABLE. CALL THE SYSTEM MANAGER. AGAIN, IF IT OCCURS THEN THE TAPE MAY BE IRRECOVERABLE. CALL SYSTEM MANAGER. "" READ 008 THE END OF TAPE WAS REACHED. MOUNT THE FOLLOWING TAPE TO READ THE REMAINING PORTIONS OF THE CARTRIDGE. TO CONTINUE THE PROGRAM ENTER "GO". TO HALT THE PROCESS ENTER "AB". NOTE HOWEVER THAT A REPLY OF AN "AB" WHEN RUNNING READT WILL CAUSE AN INCOMPLETE CARTRIDGE TO BE PRESENT ON THE SYSTEM. "" READ 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. "" READ 010 YOU ARE OPERATING IN A NONSESSION ENVIRONMENT. AN LU MUST BE SPECIFEID (NEGATIVE LU) SINCE THERE ISN'T A FREE DISC POOL. ""