RE: More on "Transfer ID" was: QMGTOOLS

I seem to have the same issue.

When I run from a command line and insert my password string I get:
String 'longpasswordhere' contains a character that is not valid

If I prompt, I get no such message.
I'm currently not able to send anything to IBM using MGTOOLS.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Bryan Dietz
Sent: Wednesday, October 12, 2022 5:41 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: More on "Transfer ID" was: QMGTOOLS

Thanks for this Rob.

now for the stupid stuff.

why bother storing the transfer ID if the FTP2IBMCMD does not seem to use the stored credentials?

--
bryan


Rob Berendt wrote on 10/4/2022 9:48 AM:

QMGTOOLS allows you to store the transfer id with GO QMGTOOLS/MG
option 25. Store FTP2IBMCMD credentials This is the command:
STORFTPPWD IBMID() IBMPWD() IBMPWD2()
IBMPWD2 is simply a double entry of IBMPWD since it's nondisplay.

Now, the following is important information.
IBM recommends you do 13. Check IBM for updated QMGTOOLS or CMPVER each and every time you use mgtools to ensure you have the latest version. And updates will be pouring out.
Each time you update it the update will wipe out the stored transfer id. So basically run this process:
ADDLIBLE QMGTOOLS
STORFTPPWD IBMID() IBMPWD() IBMPWD2()
CMPVER
STORFTPPWD IBMID() IBMPWD() IBMPWD2()
Then get to work on what you want to use the tool for.

Just got off the phone with the guy who works on this stuff.
Some updates:
FTP2IBMCMD. Parameter FTPTYPE. *IBMSDDUU is obsolete and will just be substituted under the covers with another value. It won't be removed since it will break stuff. *STDFTP, yeah, not going to work.
Basically the encryption for *IBMSDDUU was kind of proprietary and doesn't really pass muster.

This transfer id will be needed for lots more, like using sftp to ibm from your hmc.

Rob Berendt