On Tue, 19 Oct 2021 02:57:22 -0500, Jantje. <[email protected]> wrote:

>On Mon, 18 Oct 2021 15:17:22 -0400, Billy Ashton wrote:
>
>>Hi again...is there a way to run a single BPXBATCH JCL member that
>
>Can I suggest you move to COZBATCH? So much simpler to use and far better 
>functionality IMHO.
> 
A good idea provided that the programmer is entitled to haven COZBATCH 
installed.


On Mon, 18 Oct 2021 15:17:22 -0400, Billy Ashton wrote:

>Hi again...is there a way to run a single BPXBATCH JCL member that
>copies some instream data into temp files and then run a command that
>uses those files?
>
>For example, I tried this, but got no output:
>//SFTP      EXEC PGM=BPXBATCH
>    ...
>//STDPARM   DD *,SYMBOLS=(JCLONLY)
>sh cat > &PATH/pwd.sh   << EOF1
> 
Your STDPARM should begin with SH or PGM.

>echo '&PASS'
>EOF1
>
Trailing blanks will caus EOFn not to bee recognized.
Perhaps better IKJEFT01 with several REPRO commands
to create the temp files.

Create all the temp files in a single temp directory.
delete it with "rm -r" allowing design flexibility.

I'll suggest putting sensitive variables in STDENV, avoiding
even momentary existence in the temp file.

>sh cd &PATH;
>
"sh" causes the "cd" to be performed in a separate
execution environment, having no practical effect.

># ---------- 3. Download the file from the server
>get &SRVNAME
># ---------- 4. Copy the file from the unix HFS to z/OS
>!cp &SRVNAME "//'&FTP$'"
>
Can't FTP download directly to an MVS data set or even
a DDNAME,  requiring no temp file or copy/

>Also, before you ask, because of the highly sensitive nature of this
>server, the passwords are changed at a very high frequency, and they
>elected to use user/password authentication as keys do not allow the
>time-restricted access they need.
>
Can't keys be changed as frequently as passwords?

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to