Re: SNDPTFORD *Image failed -- MIDRANGE-L

no messages in qservice

the following message in job QESECIMG and it (to me) makes no sense. I
ordered SNDPTFORD *CUMPKG, which for V7R1 is SF99710. In addition, the
process did download
C5142710.txt STMF
C5142710_1.bin STMF
C5142710_2.bin STMF
which is at least part of the cume for 7.1.

CPI8C02 Diagnostic 00 10/13/15 19:36:16.909820
QESECARE QSYS *STMT QESECARE QSYS
From module . . . . . . . . :
QESECARE
From procedure . . . . . . :
SendMsg__FPcT1iT1
Statement . . . . . . . . . :
57
To module . . . . . . . . . :
QESECARE
To procedure . . . . . . . :
SendMsg__FPcT1iT1
Statement . . . . . . . . . :
57
Message . . . . : PTF
*ONLYPRD-SF99710 *ONLYRLS not available on the service
provider
system.
Cause . . . . . : The program
temporary fix (PTF) you requested, PTF SF99710
for product *ONLYPRD at release
*ONLYRLS is not available on the service
provider system. Recovery . . . :
Verify the PTF number was typed
correctly. If not, type the correct
PTF number, and try your request again.
If you typed the PTF number
correctly, contact the service provider and
verify PTF SF99710 has been
ordered.

This IBM doc describes the error and seems to contradict my error.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1015861

I am resending order with SF99710 instead of *CUMPKG (if no further
suggestions). btw - I've used *CUMPKG before without issue.

Jim

On Wed, Oct 14, 2015 at 12:28 PM, <rob@xxxxxxxxx> wrote:

Then roughly 106 minutes after that job another job should have started.
Look for a new job around that time in DSPLOG. Or you can see if ANY
messages appeared in QSERVICE and see what job placed that message in the
message queue and then look for that job.

Once you find that job, try looking at it's joblog.

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: Jim Franz <franz9000@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/14/2015 12:22 PM
Subject: Re: SNDPTFORD *Image failed
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

The job finished at 14:04 and the downloads commenced later with 19:36
being last entry in problem history

CPC8C10 Completion 00 10/13/15 14:04:00.752365
QESECARE QSYS *STMT QCMD QSYS
From user . . . . . . . . . :
QSECOFR
From module . . . . . . . . :
QESECARE
From procedure . . . . . . :
SendMsg__FPcT1iT1
Statement . . . . . . . . . :
57
Message . . . . : Optical image is
being created for download.
Cause . . . . . : You requested an
order to be delivered as *IMAGE. Optical
image is being created for download
at IBM. Download process will start in
106 minutes. CPZ8C15 message will
be
sent to QSERVICE message queue (or the
message queue specified in the
Service Attributes) when download is

complete.

CPC8C04 Completion 00 10/13/15 14:04:01.305353
QESECARE QSYS *STMT QCMD QSYS
From user . . . . . . . . . :
QSECOFR
From module . . . . . . . . :
QESECARE
From procedure . . . . . . :
SendMsg__FPcT1iT1
Statement . . . . . . . . . :
57
Message . . . . : PTF order
complete. The PTF order ID number is H19866990.
Cause . . . . . : The PTF order
associated with problem record 1528648071
has been sent to IBM service
support. The PTF order identification assigned
number is H19866990. To see the
results, use the Work with Problem (WRKPRB)
command or the Display Problems
(DSPPRB) command.

Normal end to job log.

On Wed, Oct 14, 2015 at 12:07 PM, <rob@xxxxxxxxx> wrote:

Anything in the joblog of the job issuing the SNDPTFORD?

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: Jim Franz <franz9000@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/14/2015 11:59 AM
Subject: SNDPTFORD *Image failed
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

How do I determine why a SNDPTFORD *CUMPKG *Image failed?
WRKPRB does not indicate a job or log to look at.
Nothing in QSYSOPR or QSERVICE msgq
Nothing in QHST log during that time
I do have several text and bin files in directory

Problem ID . . . . . . . : 1528648071
Current status . . . . . : SENT
Problem . . . . . . . . : Preventative fix package request

Date and time ordered . . . . . . : 10/13/15 14:00:05
Filter name . . . . . . . . . . . : QS9FILTER
Library . . . . . . . . . . . . : QSRVAGT
Group assigned . . . . . . . . . : *DEFAULT
Answer received . . . . . . . . . : PTF order cannot be processed.

Order ID . . . . . . . . . . . . : H19915914
PTF order status . . . . . . . . : FAILED
PTF order options:
PTF parts . . . . . . . . . . . : *ALL
Order . . . . . . . . . . . . . : *REQUIRED
Reorder . . . . . . . . . . . . : *NO
Delivery method . . . . . . . . : *ANY
Delivery format . . . . . . . . : *IMAGE
Image directory . . . . . . . . : /fixes

Image prefix . . . . . . . . . : *SRVPVD
Image option . . . . . . . . . : *DOWNLOAD
Image catalog name . . . . . . : PTFCATALOG
Problem category . . . . . . . . : *REPORT
Default device for PTFs . . . . . : 6331
Model . . . . . . . . . . . . . : 014

Display Problem History
S
Problem ID . . . . . . . : 1528648071
Current status . . . . . : SENT
Problem . . . . . . . . : Preventative fix package request

Date Time User ID Event
10/13/15 14:00:05 XXX Problem entry opened
10/13/15 14:00:05 XXX Prepared to report
10/13/15 14:04:01 QSECOFR Problem answered
10/13/15 19:35:38 QSECOFR Service request sent
10/13/15 19:36:16 QSECOFR Problem answered
10/13/15 19:36:18 QSECOFR Problem answered

Directory . . . . : /fixes

Opt Object link Type
groups DIR
C5142710.txt STMF
C5142710_1.bin STMF
C5142710_2.bin STMF
QIMGCLG STMF
S6990.TXT STMF
S6990V01.BIN STMF
S6990V02.BIN STMF
S6990V03.BIN STMF

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.