Re: Backup performance (CFINT) -- MIDRANGE-L

I don't recall having that problem at V3R2. I did at V4R2 & V4R3
I think this is the one I was thinking of.
You'll probably have to modify your backup program at V3R2 to allow for the error.

Item SA74975

APAR Identifier ...... SA74975 Last Changed..00/10/10
OSP-INCORROUT SAVING MESSAGE QUEUES IN BREAK MODE

Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 98/07/02
Component .......... 5769SS1SR Duplicate of ........
Reported Release ......... 430 Fixed Release ............ 999
Component Name 5769 SAVE / RES Special Notice
Current Target Date .. Flags
SCP ...................
Platform ............

Status Detail: TESTPACKAGING - Packaged solution is being tested.

PE PTF List:

PTF List:
Release 410 : SF49860 available 99/02/25 (9026 )
Release 420 : SF49848 available 98/12/20 (8342 )
Release 430 : SF49800 available 98/08/31 (8230 )

Parent APAR:
Child APAR list:

ERROR DESCRIPTION:
Message queue set to delivery *BREAK. Save of *MSGQ object
fails with MSGCPF3761 T/QSRSVPRE F/QSRSVPRE.

LOCAL FIX:

PROBLEM SUMMARY:
Message queue set to delivery *BREAK. Save of *MSGQ object
fails with MSGCPF3761 T/QSRSVPRE F/QSRSVPRE.

PROBLEM CONCLUSION:
Save processing will be corrected to save *MSGQ objects which
have delivery *BREAK set.

...Neil

Jeff Crosby <jlcrosby@fwi.com>
Sent by: owner-midrange-l@midrange.com

2000/11/07 09:18
Please respond to MIDRANGE-L

To: MIDRANGE-L@midrange.com
cc:
Subject: Re: Backup performance (CFINT)

neilp@dpslink.com wrote: > There were PTF's issued for a problem where an active (signed on user's) > message queue was not saved during backup. > What release are you running ? V3R2. Another response to me also said there was a PTF available. I searched PTF cover letters and could not find one. > Also, don't forget that not saving a message queue isn't a show stopper > anyway. If you had to restore from the backup, the message queue would be > recreated the first time the user signed on anyway. Chances are any > messages in the message queue would be too old to be of use by then > anyway. Understood on the show stopper. But, my program does MONMSG for problems and this causes an *ESCAPE message that not all objects were saved. -- -Jeff The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so.

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.