× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jim

You might look into the system reply list - you might want to be careful to ensure that the reply applies to this situation only. You can specify a match for a substring in the message text to help with this.

But this means that the backup job has to be set up to use reply list for messages. Not default. You can also change the default on this message, but let others respond to implications for that. That would affect everyone. Reply list would apply only to jobs where you set the job to use a reply list.

HTH
Vern

Jim Franz wrote:
offline - thanks for the info. I have a 2nd question related to this, and to me it sounds a little strange - this Save System issue has happened 2 months in a row, and both times the cpf3777 error of a problem with the save is issued, and (because no one is in the building at the time) the msg sits on the console (twinax), and both times the default reply (C) appears in the job log 22+ hours later. I can see the timestamp in the joblog. 1st month it was 22 hrs, this month, 25 hrs later.
I know if someone just pressed ENTER it would take the default, but according to the manager, no one was in the building either time. This is a 24x7 operation, except Saturday noon to Sunday noon and once a month they start a Save All (go save opt 21) and leave. For years this has worked till this error.
Is there anything in OS that would take the default reply after xx hours?
Nothing monitoring the sysopr queue.
No special schedule jobs.
Endsbs *all is successful.
It is twinax and I wondered if a power blip might in some way be seen as ENTER..?
No power schedule jobs
No backup schedule jobs
V5R4 w/cume thru 08183 (installing latest cume soon)
Jim Franz

----- Original Message ----- From: "Kirk Goins" <kgoins@xxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, September 07, 2009 1:33 AM
Subject: Re: CPF3285 Damage File QAYPSYSTEM in QMGTC


Jim Franz wrote:
For 2nd month in a row customer's Save System halted with
CPPF3285 on a damaged file QMGTC/QAYPSYSTEM.
I did a RCLLIB on QMGTC thinking it would solve the problem.

I should have read this post from Rob in 2006 with a temp
workaround from IBM:
http://archive.midrange.com/midrange-l/200604/msg00618.html

ENDTCPSVR *MGTC
2 Delete the following files in order:
QMGTC/QAYPSGRPCT
QMGTC/QAYPSYSGRP
QMGTC/QAYPSYSTEM
3 On the i5/OS command line type the following:
CALL QSYS/QYPSSETUP PARM(V5R3M0)
Press the Enter key. This program will re-create the files, redo all
constraints, and start journaling.
4 On the i5/OS command line type the following:
STRTCPSVR *MGTC

My question is (since it points to V5R3 in the call parms) if this
is still the recommend for V5R4 and V6R1?

Jim Franz

Jim,
Searching on QAYPSYSTEM from the main iSeries Support page gets a hit
requiring an IBM ID to access.. long story short is the tip shows the

CALL QSYS/QYPSSETUP PARM(V5R3M0)

with V5R3M0 or V5R4M0 or V6R1M0 so you it valid for all 3 releases


--
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.