Re: What was the last volume used on a save

Well the earlier suggestion of PRTERRRPT should list all the volumes used,
and, the byte count written.

On Tue, Mar 18, 2025 at 8:01 AM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I am saving to multiple volumes due to subsequent step where all used
volumes have to be copied. Each volume has a specific maximum size.

Get Outlook for iOS<https://aka.ms/o0ukef>Don Brown

Senior Consultant




OneTeam IT Pty Ltd
P: 1300 088 400

________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Rob
Berendt <robertowenberendt@xxxxxxxxx>
Sent: Tuesday, March 18, 2025 9:45:38 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: What was the last volume used on a save

1 - Change the job to stop putting the joblog to output queue. If you want
(there is no need) a printed joblog you can always do a DSPJOBLOG
OUTPUT(*PRINT) at the end. Printed ones are stone knives and bearskins.
Otherwise, if you're into knapping flint, you can try

https://www.ibm.com/docs/en/i/7.5?topic=services-spooled-file-data-table-function
.

Or, there is this option:
PRTERRLOG TYPE(*VOLSTAT)
OUTPUT(*OUTFILE)
OUTFILE(QTEMP/VOLUMEUSED)
VOLTYPE(3580)
VOLSTAT(*KEEP)
VOLSTATTYP(*SESSION)
Specifying 3580 when you're using LTO7 seems nutty but if you have a better
alternative I'm all ears.

Let me see if I have your wording correct. You said "How can I determine
what was the last volume used by the save." Are you saving to multiple
volumes or did you mean to say "How can I determine the volume used by the
last save?"?


On Tue, Mar 18, 2025 at 12:43 AM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

System is V7R5

We are NOT using BRMS

Running a save with multiple volumes.

How can I determine what was the last volume used by the save.

Currently joblogs are on the output queue - NOT in *Pending status.

I could copy the joblog to a file and parse the file looking for the last
volume name message but I was hoping there may be a better option.

Any suggestions or comments appreciated.

Thanks
Don


Brisbane - Sydney - Melbourne


Don Brown

Senior Consultant




P: 1300 088 400




DISCLAIMER. Before opening any attachments, check them for viruses and
defects. This email and its attachments may contain confidential
information. If you are not the intended recipient, please do not read,
distribute or copy this email or its attachments but notify sender and
delete it. Any views expressed in this email are those of the individual
sender
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
Message protected by MailGuard: e-mail anti-virus, anti-spam and content
filtering.
https://www.mailguard.com.au


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.