Does a SAV command initiate a cleanup

485 pts.
Tags:
AS/400 backup
IFS
SAV commands
I recently added the SAV command to our regular backup to save our IFS. While testing the backup I noticed at the bottom right of my display the message "Cleanup step 8 of 11." I have been unable to find out what was being cleaned up or if it was related to the command I added. There is no mention of it in my log or history. We do not use the GO CLEANUP facility and it seems to be the only thing I can find reference to. Thanks in advance.

Software/Hardware used:
V5R4

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 17  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    The message would seem to be CPI372A from QCPFMSG and is normally part of a system "cleanup" operation. I'm not aware of it having any connection to a SAV command. How were you "testing the backup"? Did you call it from an interactive session? Submit it to batch? Have you reviewed the backup programming to see if CPI372A is referenced anywhere? Are any messages sent to the *EXT message queue in the backup programming? (SNDPGMMSG or the QMHSNDPM API might be seen.) Tom
    125,585 pointsBadges:
    report
  • JaneS
    Hi Tom Thanks for your timely response. The backup is an interactive job. I have no reference to CPI372A or SNDPGMMSG. I refer to the SAV command only because it is the most recent change in the program. Previously we add the SAVDLO and a SAVLIB that takes care of our OUTQs and SPLFDTA but we never noticed this message in the testing of these changes. That is not to say that the message has not appeared before only that we have not seen it as the job runs overnight without operator intervention. What kind of system cleanup are you referring to?
    485 pointsBadges:
    report
  • TomLiotta
    What kind of system cleanup are you referring to? That would be the standard cleanup that is configured, scheduled and initiated through the GO CLEANUP menu. Have you done multiple tests? Did the message appear in each test? If so, was it always for step "8 of 11"? If you see it again, make sure you get the detailed {help} for it in order to capture the to and from program names. Technically, there might be a minor bug in the SAV command. Tom
    125,585 pointsBadges:
    report
  • Splat
    Are you using save-while-active by chance? I'm wondering if that message has anything to do with save-while-active checkpoints.
    7,235 pointsBadges:
    report
  • JaneS
    The SAVACT parm in the command is set to *NO. I have not rerun the test since this message because I was not sure what was being done/ cleaned up. When it originally appeared I tried to get details on the message but wasn't able to prompt on it (not sure why) and displaying the job showed nothing.
    485 pointsBadges:
    report
  • Splat
    There's no second-level text for CPI372A, so determining the reason for it is less than easy. As this is a SAV operation, it may have to do with the steps necessary to save objects outside of the QSYS.LIB portion of the IFS.
    7,235 pointsBadges:
    report
  • TomLiotta
    There’s no second-level text for CPI372A, so determining the reason for it is less than easy. It wouldn't be 2nd-level text that would be of interest. It would be the name of the program that sent the message and the name of the program it was sent to. However... When it originally appeared I tried to get details on the message but wasn’t able to prompt on it (not sure why) and displaying the job showed nothing. This would be the normal condition of a *STATUS message. If CPI327A was sent as a *STATUS message to an interactive workstation session, i.e., to *EXT, then the session would be locked because the program/command was active and there'd be no way to get message details. And the message would disappear when the program/command finished. It wouldn't be in the joblog. But I have no idea what SAV would be doing sending that message identifier. Well, technically I can think of one way -- OVRMSGF could cause that text to be sent in place of some other text if one of the usual SAV messages was overridden. But that doesn't make much sense to do. It could also happen if there's a bug in SAV such that it sends CPI372A instead of, say, CPF372A. (Not likely; that's just an example.) Causing it to happen again means there's a chance of getting IBM involved. If it can be done in a workstation session, then it should also happen in SBMJOB. If it happens when submitted, then the message might get logged or be routed to QSYSOPR. If so, then the message details ought to be available from there. Tom
    125,585 pointsBadges:
    report
  • JaneS
    Hi. Was finally able to continue my testing. The CPI372A message comes up each time I run the backup. On my last test I monitored the job stack as it was completeing the SAV command. Here is what I found. In the job stack there is an entry for a program called QSRSAV QSYS and under the procedure column there is an entry for : qsrFS_CleanupSAV__Fv. Sound like anything familiar? Seems like this procedure is what generates the message. Note that the CPI372A message comes up even if I set the GO CLEANUP option to N=No for no cleanup.
    485 pointsBadges:
    report
  • TomLiotta
    The CPI372A message comes up... Interesting. I might run some tests to see if I can cause it to happen. If it's sent as a *STATUS message, then it ought to be possible to monitor for it. Note that you probably don't want to monitor for it since it would likely interrupt the process. It's possible that no one noticed it before because backups often run in batch or without anyone watching *STATUS messages go by. Tom
    125,585 pointsBadges:
    report
  • JaneS
    Hi Tom. I do not want to monitor for the message so that will not be an issue. My concern is "What is it cleaning up". Our shop has it's own set of guidelines as to what and when things are cleaned up. We don't want any unexpected surprises because IBM assumes it's more convenient for the user. If it's cleaning up temp files used to do the SAV, fine no problem. That is what I am trying to find out. Thanks for your feedback. It is much appreciated.
    485 pointsBadges:
    report
  • TomLiotta
    @JaneS: First tests don't detect CPI372A, but they're necessarily simple just to get the programming started. Can you provide the SAV command that you expect to run? Tom
    125,585 pointsBadges:
    report
  • JaneS
    I wonder if the type of screen I'm using to run it would make a difference in seeing the status message, I'm using an older twinax connected dummy screen. I haven't tried to run it from a PC using emulation. Because of time out it could get kicked off before completion. The command I'm using is: SAV DEV('/qsys.lib/QTAPE5.devd') OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT)) EXPDATE(&QDATEX) ENDOPT(*LEAVE) UPDHST(*YES) DTACPR(*YES) The &QDATEX variable is just a date calculated a week from the date being run.
    485 pointsBadges:
    report
  • TomLiotta
    OBJ((’/*’) (’/QSYS.LIB’ *OMIT) (’/QDLS’ *OMIT)) Possibly minor item -- are you sure that you don't want to *OMIT /QNTC? Also, since you mention PC emulation, this appears not to be a restricted state nor quiescent system save, so are you sure you don't want to *OMIT /QIBM/ProdData? (Possibly all of /QIBM.) I'll see about further tests. Tom
    125,585 pointsBadges:
    report
  • JaneS
    No this is not a restricted state backup. It is a standard nightly backup we do so I try to include as much as possible without the restricted state. Thanks for the suggestion and appreciate your effort in trying to help me with the answer.
    485 pointsBadges:
    report
  • Whatis23
    Sorry to jump into this so late. Our night operators perform an option 21 (Full Save) or 23 (*ALLUSR) plus option 11 (SAV).every night. That cleanup message comes up every time before completion. They called IBM and it was stated a cleanup of temp objects created for the backup were being deleted.
    5,665 pointsBadges:
    report
  • TomLiotta
    That cleanup message comes up every time before completion. They called IBM... It's certainly good to know that this is normal. I'll probably do some digging on my private systems to see how much of a picture I can build up of what happens. I'd say that you should enter your comment as the "Answer". I can't see much chance of improvement. Tom
    125,585 pointsBadges:
    report
  • JaneS
    Well thanks to you both for the help on this question. You've been very helpful. I now feel confident in running the command without loosing any info unexpectedly. Thanks again.
    485 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following