|
I run SYS120C quite frequently in 405 CD in a controlled setting in which NO OTHER USERS are on BPCS at the time that it is running. I always wait until I get the successful job end report, which lists the files that got actually reorganized, before doing anything else with the files. The way I run it is F6 F18 F6 F6 so that all files that need reorg get reorg. My suggestion to you is 1. Get yourself to such a controlled state, like right after a backup. 2. Pop-Up Menu-1 change your JOBQ to ON HOLD 3. Launch SYS120C to JOBQ 4. Pop-Up Menu-7 change the SYS120C job ... F10 2nd screen, change JOBQ to 4 0 *SECLVL & change LOGCLPGM to *YES ... then release the SYS120C job to run ... then Pop-Up Menu-1 change your JOBQ back to normal You will get a JOBLOG that has a whole lot more information than what you shared with us. When you figure out why this is failing, it will probably lead to discoveries about other things failing that you were not aware of. Although you SAY you running this with all stuff correct, something has changed ... perhaps someone changed YOUR security & you not know it. Understanding this requires technical knowlege of both BPCS & AS/400. MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac) AS/400 Data Manager & Programmer for BPCS 405 CD Rel-02 mixed mode (twinax interactive & batch) @ http://www.cen-elec.com Central Industries of Indiana--->Quality manufacturer of wire harnesses and electrical sub-assemblies - fax # 812-424-6838
- Subject: BPCS Reorg job
- From: RickCarter@xxxxxxxxxx
- Date: Mon, 2 Apr 2001 15:37:54 -0500
AS400 Mix Mode BPCS V6.1.01 Job SYS120C has stopped running successfully. This job was running fine but I noticed today that it wasn't running anymore. I can't say when it stopped running as it doesn't really give a noticeable error msg and the operator did not catch this. When I run this in a controlled environment today, I captured the msg below but it doesn't tell me much or I don't understand what it's telling me. I am running this with the correct lib list and all object authority. It says there is a file missing from BPCSF but it doesn't say which file it is. Does anyone know if there's some type of system file residing in BPCSF that has anything to do with the SYS120C job running. Basically the msg below is what is showing in the joblog. Message . . . . : -CALL SYS126 PARM('BPCSF ' 'Y' 'N' 'N' ' ') 40 04/02/01 13:58:44 QLIROHDL QSYS 00D8 SYS126 B Message . . . . : File in library BPCSF not found. Cause . . . . . : The file name or the library name is not correct. If th library name was not specified, the file may be in a library that is not contained in the library list. Recovery . . . : Correct the file or library name, or add the library name to the library list. Then try the request again. 40 04/02/01 13:58:45 QMHUNMSG *N SYS126 B Message . . . . : Function check. CPF9812 unmonitored by SYS126 at stateme 74300, instruction X'030C'. Cause . . . . . : An escape exception message was sent to a program which did not monitor for that message. The full name of the program to which th unmonitored message was sent is SYS126 . At the time the message was sent the program was stopped at higher level language statement number(s) 74300 If more than one statement number is shown, the program was a bound program Optimization does not allow a single statement number to be determined. If *N is shown as a value, it means the actual value was not available. Recovery . . . : See the low level messages previously listed to locate the cause of the function check. Correct any errors, and then try the request again. +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.