|
Some people use a custom save routine that monitors and skips critical messages like that. I've seen it. "Backup didn't end in a MSGW. Must have ran ok. And, what do you know, we saved our entire system in 10 minutes." Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 05/03/2005 02:27 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc Subject RE: CPF4182 on copy Doug, I've done some searches and they point to object corruption, probably on your V5R1 machine. Here are some links I've hit upon: http://tinyurl.com/drnrm http://tinyurl.com/dgk3s http://tinyurl.com/9j4b5 But when I think about it, the save process (SAVLIB) should have detected damaged objects, so maybe this is a brand new V5R3 problem. Hard to tell, especially with the fact that it only fails from a command line within your application. Is it possible your app is stomping on some storage it shouldn't? I'm afraid I'm not being very helpful. Elvis -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ritsema, Doug B Sent: Tuesday, May 03, 2005 10:28 AM To: 'Midrange Systems Technical Discussion' Subject: RE: CPF4182 on copy This is the message. What I just discovered is that I am only having problems if I try it from a command line within my application. When I exit my application it works normally. Message ID . . . . . . : MCH3601 Severity . . . . . . . : 40 Date sent . . . . . . : 05/03/05 Time sent . . . . . . : 10:54:59 Message type . . . . . : Escape >From . . . . . . . . . : DBR CCSID . . . . . . . . : 65535 >From program . . . . . . . . . : QDMCOPEN From library . . . . . . . . : QSYS Instruction . . . . . . . . : 128F To program . . . . . . . . . . : QDMCOPEN To library . . . . . . . . . : QSYS Instruction . . . . . . . . : 128F -----Original Message----- From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, May 03, 2005 11:09 AM To: 'Midrange Systems Technical Discussion' Subject: RE: CPF4182 on copy I am sorry Doug, I meant on the MCH3601 message screen. So after you hit F1 on MCH3601, then hit F9 on it. Again, sorry for not being clear. Elvis -----Original Message----- Subject: RE: CPF4182 on copy Display Message Details Message ID . . . . . . : CPF4182 Severity . . . . . . . : 50 Date sent . . . . . . : 05/03/05 Time sent . . . . . . : 10:54:59 Message type . . . . . : Information From . . . . . . . . . : DBR CCSID . . . . . . . . : 65535 From program . . . . . . . . . : QUOCMD From library . . . . . . . . : QSYS Instruction . . . . . . . . : 0464 To program . . . . . . . . . . : QUOMAIN To library . . . . . . . . . : QPDA Instruction . . . . . . . . : 10FF Time sent . . . . . . . . . . : 10:54:59.043976 Bottom Press Enter to continue. F1=Help F3=Exit F12=Cancel -----Original Message----- Can you hit F9 on this screen and post the display? -----Original Message----- Subject: CPF4182 on copy Moving from V5R1 to V5R3. Restored the library from tape. Getting a CPF4182 when I try to copy a program in PDM but I can open the program and save it with a different name. Message ID . . . . . . : MCH3601 Message . . . . : Pointer not set for location referenced. Cause . . . . . : A pointer was used, either directly or as a basing pointer, that has not been set to an address. File HAWSRC in library HAWPGM member or device LOADXX not opened. Error opening file HAWSRC in library HAWPGM. It looks like the MCH3601 is causing the CPF4182. Any ideas what might be causing this? TIA Doug Ritsema Holland American Wafer Co. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.