Re: SAVSYS & Break Messages - V5R4

The CPF3285 is issued by the database [save processing] to diagnose an unexpected /addressing/ condition while navigating the *FILE object; typically member-to-member, possibly for-number-of-members. What was done to effect the "delete and replace" is insufficiently defined; DLTF & CRTPF or RSTOBJ, and were the joblog for each action reviewed for errors? Note that /delete/ is /tolerant/ of errors, and will issue a completion even if errors transpired during a DLTF request; such errors may leave consequences which effect failures for the new *FILE, possibly during RSTOBJ. Was the failing save repeated just after the /recovery/ [by "delete and replace"]? It is possible that the new *FILE would already be exhibiting the error during save, immediately, rather than the file only later becoming "damaged before the day is over."; e.g. due to the delete requesting /completing, but with errors/.

Regards, Chuck

Cyndi Bradberry wrote:

<<SNIP>>

I do know the file that is causing the problem. It is a JDE file
(F98301 - Dream writer Parameter file). We have 4 versions of JDE
on our system, and only one is damaged. If we delete and replace
with one of the good versions, it is damaged before the day is
over. We are still trying to figure out what is causing the
problem.

The prior messages are CPF3285 Damaged File & CPF3741 File not
saved. I'll talk to my administrator about putting these into the
reply list when he next does a savsys.

Jerry Draper wrote:

This should work:

When setting up DSP01 with the delayed savsys21 do the following:

ADDRPYLE SEQNBR(xxxx) MSGID(CPA3708) RPY('G')

CHGJOB INQMSGRPY(*SYSRPYL) BRKMSG(*HOLD)

Confirm the following settings with option 21 from the save menu:

Devices TAP01
Prompt for commands N
Check for active files N
Message queue delivery *NOTIFY
Start time <set to time you want save sys to start>
Vary off network servers *NONE
Unmount file systems N
Print system information N
Use system reply list Y