RE: image catalog problem on V7R1 SF99710 -- MIDRANGE-L

Jim,

My CUM, TR, and all Groups are current.

But my resave level is RE13015 - RS-710-G, 9 levels back.

Do I need to be concerned about updating or getting current resave - RE16082 - RS-710-S?

I will be going to V7R3 within 6 months, which will include the latest V7R3 resave.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Tuesday, November 21, 2017 9:42 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: image catalog problem on V7R1 SF99710

Paul,

Highly unlikely but possible. Honestly I've not seen the issues described

in this thread and we do this process 10 times/month.

Everyone:

First at V7R1 unless PTFs have not been applied for literally years, the code on the system would be at the most recent resave anyway, so I'm not

sure why the concern with it. Remember PTFs will bring the system up to

that level. Download the new ones and you have what you need.

My thinking is there is a fault somewhere in the download or process to

build the image catalogs. I'd reorder, download with FTP (and FTP only!

And DO NOT use FileZilla!) and try it again. Download Director and direct download with SNDPTFORD cause us so many more issues that I've stopped any of our technicians from using those. The corruption rate on those downloads is very high, and the image catalog will verify since that process does not dig all that deep into the images.

Sometimes Stone Age tools just work the best. (How many times while camping did you just use a rock instead of going all the way back to the truck for a

hammer?)

--

Jim Oberholtzer

Agile Technology Architects

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul

Sent: Tuesday, November 21, 2017 8:28 AM

To: 'Midrange Systems Technical Discussion'

Subject: RE: image catalog problem on V7R1 SF99710

Rob,

Maybe I asked the wrong question.

Can you have all the latest code contained in the latest resave, (ordered from MF PTFs), but the resave marker PTF is old because a resave wasn't ordered.

Paul

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt

Sent: Tuesday, November 21, 2017 8:28 AM

To: Midrange Systems Technical Discussion

Subject: RE: image catalog problem on V7R1 SF99710

Paul,

Did you really want to know how to check what level of resave one is at?

Or, were you trying to tell me that people will not bother to chase down a link, such as the one I posted

http://www-01.ibm.com/support/docview.wss?uid=nas8N1022066

and that I need to put the instructions in the message body? And that is why you had your instructions right below your question?

Rob Berendt

--

IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail

to: 2505 Dekko Drive

Garrett, IN 46738

Ship to: Dock 108

6928N 400E

Kendallville, IN 46755

http://www.dekko.com

From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx<mailto:PSteinmetz@xxxxxxxxxx>>

To: "'Midrange Systems Technical Discussion'"

<midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>

Date: 11/21/2017 08:22 AM

Subject: RE: image catalog problem on V7R1 SF99710

Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>>

Rob,

How can one tell what your current resave level is?

V7R1, I'm on latest TR Level -11, latest CUM, 17192.

The marker PTF for the resave is old- RE13015

Paul

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt

Sent: Tuesday, November 21, 2017 7:58 AM

To: Midrange Systems Technical Discussion

Subject: Re: image catalog problem on V7R1 SF99710

<snip>

It was latest slip from last week.

</snip>

Bull<excrement>

IBM hasn't generated a new resave for IBM i 7.1 since May of 2016.

I didn't ask when you downloaded it, put it on, etc. I asked what level of resave it was.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1022066

But if your point is that you downloaded it just last week from ESS then you're "probably" at the latest resave. However, I follow the "trust, but verify" mentality.

Rob Berendt

--

IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail

to: 2505 Dekko Drive

Garrett, IN 46738

Ship to: Dock 108

6928N 400E

Kendallville, IN 46755

http://www.dekko.com

From: "Art Tostaine, Jr." <atostaine@xxxxxxxxx<mailto:atostaine@xxxxxxxxx>>

To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>

Date: 11/21/2017 07:51 AM

Subject: Re: image catalog problem on V7R1 SF99710

Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>>

Thanks rob. It was latest slip from last week. I found one Ptf and it was applied.

I will call ibm this morning

On Tue, Nov 21, 2017 at 7:21 AM Rob Berendt <rob@xxxxxxxxx<mailto:rob@xxxxxxxxx>> wrote:

If you do a DSPPTF can you tell what level of resave of 7.1 you just

slip

installed on your system?

http://www-01.ibm.com/support/docview.wss?uid=nas8N1022066

I would think a recent resave would have most of those image catalog

issues beat into submission. If you are on a more recent resave then

you

might want to open a ticket with IBM. The usual questions:

When you FTP'd the file to your IBM i did you use binary?

Then I would:

SIGNOFF

Sign back on.

CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES) LODIMGCLG IMGCLG(MYIMGCLG)

OPTION(*UNLOAD) RMVIMGCLGE IMGCLG(MYIMGCLG) IMGCLGIDX(1) KEEP(*YES)

- Repeat until all image catalog entries are removed.

CALL QVOIFIMG PARM('MYIMGCLG '*ALL ')

LODIMGCLG IMGCLG(MYIMGCLG) OPTION(*LOAD) DEV(MYVRTOPT) VFYIMGCLG

IMGCLG(MYIMGCLG) TYPE(*PTF) INSPTF LICPGM((*ALL)) DEV(MYVRTOPT)

INSTYP(*DLYALL) DSPJOBLOG OUTPUT(*PRINT) Use the printer output option

on the latest IBM i Access Client

solutions

to get that joblog to your PC

Attach that to the PMR when you first open it.

Rob Berendt

--

IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600

Mail to: 2505 Dekko Drive

Garrett, IN 46738

Ship to: Dock 108

6928N 400E

Kendallville, IN 46755

http://www.dekko.com

From: "Art Tostaine, Jr." <atostaine@xxxxxxxxx<mailto:atostaine@xxxxxxxxx>>

To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>

Date: 11/20/2017 08:42 PM

Subject: image catalog problem on V7R1 SF99710

Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>>

As part of my V7R3 upgrade of 4 partitions, I slip installed V7R1 on a

partition.

I want to apply the latest CUM. I had downloaded and created and

image catalog on one partition already. It loaded and verified fine.

I FTP'd the files to the latest Slip'ed partition, try to load it,

file SF99701_1.bin goes to error.

OK, FTP it again. Same thing.

Tried doing a CPY to QFILESVR.400, load it, same error.

Is it possible I need a PTF on the partition to fix image catalogs?

I've been googling but the results are mostly about how to use image

catalogs.

I'm going onto fix central next.

Any ideas while I keep searching?

Thanks, Art

--

Art Tostaine

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe,

unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take

a moment to review the archives at

https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe,

unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take

a moment to review the archives at

https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--

Art Tostaine

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:

http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:

http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD