MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

RE: how to escalate IBM software support ticket



fixed

Jim,

All our 3995 converted platters are in one IFS folder, and subfolders.
Not part of any image catalog.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of franz9000
Sent: Thursday, June 05, 2014 11:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: how to escalate IBM software support ticket

we do shutdown the conversion process before save.
Also end all communications and subsystems (basically our version of a endsbs *all-we have many client apps making sql calls into the DB2 and we need to cut all that off to get a good save) We still do SAVACT just in case some IBM process still in use.
I know there are issues with IFS locking but they did put the parm on the SAV cmd...
which why we go to all the issues of ending subsystems.

If you went through this 2 years ago, do you unload the catalogs prior to the save?
We were told it was not required.
I have saved individual catalogs to save file to take the tape drive out of the process.
Also have saved single catalogs to tape.
Jim



----- Original Message -----
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, June 05, 2014 11:06 PM
Subject: RE: how to escalate IBM software support ticket


Jim,

I would wait till the conversion is done building.
Trying to save IFS objects in use does lead to issues.
SWA does not apply to IFS objects.

We did a similar 3995 conversion two years ago, once converted, results
were good.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
franz9000
Sent: Thursday, June 05, 2014 10:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: how to escalate IBM software support ticket

BRMS no (but planned)
SAV DEV('/QSYS.LIB/TAP06.DEVD') OBJ(('/*') +
('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT)) +
SAVACT(*YES) SAVACTOPT(*ALL) +
ENDOPT(*LEAVE) UPDHST(*YES)

The image catalogs are our conversion of 3995 Image Drive cartridges (350
platters x 2 sides = 700 catalog entries) using IBM Services api for
conversion. We have 8 image catalogs each with 100 catalog entries
(representing each platter side) This conversion is still building - it's
close to a terrabyte of images Jim

----- Original Message -----
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, June 05, 2014 10:37 PM
Subject: RE: how to escalate IBM software support ticket


Jim,

A few questions.
BRMS - yes or no?
How are saving IFS, QALLUSRLNK, *LINK, or other
SWA - yes or no?

Paul


----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jim
Franz
Sent: Thursday, June 05, 2014 10:23 PM
To: Midrange Systems Technical Discussion
Subject: how to escalate IBM software support ticket

Not wanting to start a rant or war, but what to do when a critical issue
has finished two days of emails back & forth but nowhere near a
resolution.
No recommendation. Repeated request for them to call. This is first time
I
started ticket via web site.
We failed 2 days in a row (each w/different tapes) to complete a SAV,
with
tape media errors, when we changed *ALWSAV attribute on image catalogs
directory to *Yes. It made tape unusable for next step SAVLIB. All works
again when we change ALWSAV back to *NO on that directory. So far they
have said the published ptfs in this area don't match the issue.
We will test new hardware coming in next week, and I can't get a full
save
to complete...
Jim
--
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.

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


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

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







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact