DSN changes on FTP's between mainframe & PC

warren · Posted: Wed Sep 13, 2006 7:56 pm

User is currently doing get's & put's between mf & pc. They don't do mget & mput, because the DSN must change. Format example:

put c:\aabbbbbccccc00001 "'hlq.ilq.aa.bbbbb.ccccc.s00001'"

A high-level qualifer & intermediate-level qualifier must be appended to the front of the DSN's. Periods must also be inserted, breaking up the a's, b's & c's. Finally, an 's' must be inserted before the LLQ.

So the user's type them in manually and do not use mget or mput because they don't know how to define the mainframe DSN's with the PC DSN's, in a separate directory or folder. Neither do I.

My questions are: (1) how do I format multiple file DSN conversion's in FTP so that mgets & mputs can be used and/or (2) can I do this from TSO or REXX?

The problem with (2) is that I'd have to code an EXEC with a panel, etc. and have the user input the internet address of their PC, which of course would be different for each user. From the PC, the user only has to know the mainframe IP address.

I have looked in the FTP manual and also the IP User's Guide but cannot find examples of changing DSN between PC & mainframe, that was not hardcoded with just 1 file name conversion.

Someone mentioned writing a PERL script to rename the DSN's and contain the FTP commands. I don't know PERL but if the board thinks this solution would work, I would appreciate a title whereby I could pick the language up, just basically enough to do this one project.

Thanx!

raghunathns · Posted: Wed Sep 13, 2006 10:13 pm

I dont have exact solution but an alternate

ftp from pc to mainframe
if you have all files only with last qualifiers like s0001, s0002 in yout pc location. C:\ftp

ftp <login passw>
pwd -------- will give current directory in mainframe i.e user id
cd aaa
cd bbb
cd ccc
mput ------ will place all members to your pds.

mget is also same way. you receive all files as exact member names not with pds name.

will it help.

warren · Posted: Wed Sep 13, 2006 10:37 pm

These are sequential files, not PDS members. And the sequence number as the low-level-qualifier will not always be in exact order; that is, '00001' might be followed by '00002' but maybe by '00003' instead.

The user will specify the dataset names on the C: drive, in a directory or folder. I just need a script method for string manipulation of those PC dataset names into mainframe DSN's, with the periods, etc., so that the users can use an 'mget' & 'mput', instead of a straight 'get' & 'put'.