Re: sndptford *cumpkg (using image option)

You've stumbled into the reason I always use the FTP delivery method.
True if an error happens you have to restart it manually, but you'll
always know what files are needed, how big they are, and if you have
them or not.

Except for small PTFs the director download is a disaster waiting to
happen ( and usually does ).

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 8/23/2013 8:10 AM, rob@xxxxxxxxx wrote:

Message ID . . . . . . : CPC8C10 Severity . . . . . . . : 00
Message type . . . . . : Completion
Date sent . . . . . . : 08/23/13 Time sent . . . . . . :

09:00:39

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
3 minutes. CPZ8C15 message will be sent to QSERVICE message queue (or
the
message queue specified in the Service Attributes) when download is
complete.

1) When this completes, how do you know??
I reckon' about then.
2) I have files in my downloaded image directory, how do I know these

are

all of the files that I need and or are to have been downloaded.
In the past I would get messages like this in QSERVICE:
BRMSS2200.TXT optical image received and stored in a directory.
BRMSS2200V01.BIN optical image received and stored in a directory.
MISCS0918.TXT optical image received and stored in a directory.
MISCS0918V01.BIN optical image received and stored in a directory.
That .TXT file does not have a total bytes that the .BIN file will have,
unlike the ftp method. It will show you the ptf numbers downloaded.


Rob Berendt
--

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