RE: Fix Central and Download director -- MIDRANGE-L

I haven't used the FTP process before for downloading service, but I'm curious. Is the resulting file an iso image that you in turn load into an image catalog? Is that how you facilitate sharing the maintenance to other lpars via NFS/IFS?

Dana

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Thursday, July 31, 2014 8:14 AM
To: Midrange Systems Technical Discussion
Subject: Re: Fix Central and Download director

So there is a simple CL that does the FTP. It does OVRDBF INPUT to QGPL/FTPCMD and OUTPUT to QGPL/FTPLOG both with the member named in the only parameter. It then does FTP '127.0.0.1' FTPCMD and FTPLOG are source physical files.

A sample FTPCMD member looks like this:

========================================
wont work <-- attempts to log into 127.0.0.1
close <-- it fails, quit that
open delivery01-bld.dhe.ibm.com
user anonymous supersecret <- any password works namefmt 1 cd /ccss/B63923/v7r1/C <- Comes from IBM Email
lcd /ibmi/v7r1/ptf <- Where my i 7.1 PTS go
binary
mget *.bin <- Get all Binaries.
quit
========================================

The log member looks like this: (parts omitted) ========================================
Connecting to remote host 127.0.0.1 using port 21.
220-QTCP at LOOPBACK.
220 Connection will close if idle more than 5 minutes.
Enter login ID
530 Log on attempt by user WONT rejected.
Enter an FTP subcommand.

close

221 QUIT subcommand received.
Enter an FTP subcommand.

open delivery01-bld.dhe.ibm.com

Connecting to host dispby-101.boulder.ibm.com......

user anonymous

331 Guest login ok, send any password.
230 Guest login ok, access restrictions apply.

namefmt 1

500 'SITE NAMEFMT 1': command not understood.
Client NAMEFMT is 1.

cd /ccss/B63923/v7r1/C

250 CWD command successful.

lcd /ibmi/v7r1/ptf

Local working directory is /ibmi/v7r1/ptf > binary
200 Type set to I.

mget *.bin

200 Type set to I.
150 Opening BINARY mode data connection for hiper113_1.bin (3867471872 bytes).
226 Transfer complete.
3867471872 bytes transferred in 7384.260 seconds. Transfer rate 523.745 KB/sec.
quit

221-You have transferred -427495424 bytes in 1 files.
221-Total traffic for this session was -427493880 bytes in 2 transfers.
221-Thank you for using the FTP service on inetsd01.boulder.ibm.com.
221 Goodbye.
========================================

Note that when your order PTFs for download via FTP you get to pick the directory name and the file name.

For the directory name I ALWAYS use the version. V7R1 for example and you can see that in the path name IBM sends (above). This way when ordering multiple things I need not record anything, the version is in the path.

For the file name I use the group name and number. Here you can see it was Hiper group level 113 so the file is hiper113_1.bin. If it goes over one image then the next is hiper113_2.bin. Again now I know EXACTLY what this file is and can delete it after I get hiper114_1.bin some time later.

For CUMEs I use Cyjjjvrm. y last digit of year, jjj julian day, and vrm
710 for example. The yjjj is the release date for this cume. Current CUME then is C4143710_1 and _2.bin.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 7/31/2014 8:29 AM, Steinmetz, Paul wrote:

Larry,

I'd like to see one of your FTP scripts, then I want to compare the pros/cons of FTP to SNDPTFORD.
I'm still a SNDPTFORD fan.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Thursday, July 31, 2014 8:11 AM
To: Midrange Systems Technical Discussion
Subject: Re: Fix Central and Download director

Download Director, when it works correctly, is wonderful. It has a few issues like it downloads to your PC rather than directly to the system and the downloaded file names make no sense whatever. The biggest issue though is the hail of java updates recently means only 1 in 5 times can I even get the thing to run.

FTP however I have used since the dawn of Fix Central. Scripts on i that need only the directory name dropped in pull the PTFs directly to the the proper directory. No interference on my PC, uses bandwidth at the office not at home, and while it's not as fast for a single file (max about 650KB or so) I can run a big ole bunchfull of them in parallel and they each get that amount.

At one time the chief coder for Fix Central bought Jim O and I lunch at a COMMON conference as we had been helping them with design issues and testing. He informed us that IBM was intending to drop the FTP option.
Our reaction was swift and in total agreement: "No WAY! Who do we have to call!!!" Must have worked, FTP is still there!

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 7/31/2014 5:59 AM, paultherrien@xxxxxxxxxxxxxxxxxx wrote:

I was trying to download the latest cume for 7.1 yesterday and having
troubles as well. In the end, I used the FTP option.
Part of my issue was that java was failing on the PC I was using.
But what was annoying was that I could never get the Download
Director to pick up where I left off, or even just restart the
download. Fix central insisted on rebuilding my download request and
putting me off for 2 hours. After the third time I went to the FTP option.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Mike McClain
Sent: Wednesday, July 30, 2014 5:06 PM
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: Fix Central and Download director

Have been using Fix Central and Download Director to get PTF images
to my PC for years without issue.
Now, have been trying for about a week to get TR8 and cume,hiper,db
for 7.1 system. Starts out looking like everything is good using 6 to
8 connections, then after about 2-3% of first file download the
connections slowly drop off and I'll get Server busy try again later which results in the same thing.
Anyone know what's going on here?
Thanks,
Mike

Michael McClain
HICI (a Shelter Insurance Company)
--
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.

Attention: This electronic document and associated attachments (if any) may contain confidential information of the sender (SHAZAM Network) and is intended solely for use by the addressee(s). Review by unintended individuals is prohibited. If you are not the intended recipient: (i) do not read, transmit, copy, disclose, store, or utilize this communication in any manner; (ii) please reply to the sender immediately, state that you received it in error and permanently delete this message and any attachment(s) from your computer and destroy the material in its entirety if in hard copy format. If you are the intended recipient, please use discretion in any email reply to ensure that you do not send confidential information as we cannot secure it through this medium. By responding to us through internet e-mail, you agree to hold SHAZAM, Inc. and all affiliated companies harmless for any unintentional dissemination of information contained in your message. Thank you. (2)