Re: Using FTP to submit job to JES2

On 10-Sep-2014 11:23 -0500, Laine, Rogers wrote:

DBU & DFU was unavailable on my system.

AFaIK the Update Data with Temp Program (UPDDTA) has long been part of the OS.

EDTF was looking for a stream file and this is not what I wanted to
update.

To edit a fixed-length-record file, use the FILE() and MBR() parameters; specifications there, are mutually exclusive to a specification on the STMF() parameter.

I created a quick REXX to populate the PF.
One the JCL was updated I was able to run my manual FTP process and
successfully send the file to JES.

So my next issue is when running the below REXX it builds the STDOUT
but I do not see the OUTPUT from the DIR command.
Can someone explain why I do not see the output from the script?

Does that imply the data was not written to the file TEMP in SYSTEMS, and\or that the output was [also] not seen sent to the display?

The client FTP DIR subcommand should direct the output to OUTPUT, unless the "(DISK" had been coded. Note however that the Override Scope (OVRSCOPE) is unspecified on the Override requests, and the default is likely *ACTGRPDFN. The REXX runs in a [system\*NEWly] named activation. I am unsure, but the FTP client likely runs similarly; did so on v5r3.

This is the command used to run script.
STRREXPRC SRCMBR(FTPIMGTRIG) SRCFILE(QREXSRC)

/* REXX */
'CLRPFM FILE(SYSTEMS/TEMP) MBR(IMGFTPIN)'
'CLRPFM FILE(SYSTEMS/TEMP) MBR(IMGFTPOUT)'
'OVRDBF FILE(STDOUT) TOFILE(SYSTEMS/TEMP) MBR(IMGFTPIN)'
/* Say statements below are written to overridden STDOUT file above. */
Say 'SYST012 WNBXXXXX'
Say 'bin'
Say 'cd SYST012'
Say 'lcd SYST012'

Adding the following line in this position within the REXX could be helpful to enable reviewing the activation group of the FTP client work, along with the open files and overrides:

Say 'syscmd wrkjob'

Say 'dir'
/* */

Adding the following line in this position within the REXX could be helpful to enable reviewing the activation group of the REXX work, along with the open files and overrides:

'wrkjob'

'DLTOVR FILE(STDOUT)'
'OVRDBF FILE(INPUT) TOFILE(SYSTEMS/TEMP) MBR(IMGFTPIN)'
'OVRDBF FILE(OUTPUT) TOFILE(SYSTEMS/TEMP) MBR(IMGFTPOUT)'
'FTP RMTSYS('10.50.10.10') PORT(21)'
Exit

That script, effectively unaltered except correcting the "FTP" invocation to deal with unescaped apostrophes, worked fine for me on v5r3; the contents of the FTP subcommand DIR were found to be redirected to the TOFILE() for the OUTPUT device. That was with default of OVRSCOPE(*ACTGRPDFN) for the OVRDBF [and default of LVL(*) for the DLTOVR]. However, I would suggest adding OVRSCOPE(*CALLLVL) to the Override To Database File (OVRDBF) requests to avoid any issues due to the implementation details of the REXX and FTP.

Notes:

Per use of the same file for both input and output, the FTP session driven by INPUT could be [negatively] impacted by additional data being added to the member used for input [by the operation(s) using the same member for output]. Not being in control of how the FTP reads and writes, the effects seen in testing are subject to change as a side effect of changes in the implementation of the FTP; best to avoid any dependence on implementation details.

The Delete Override (DLTOVR) request, unless LVL(*JOB), is likely moot.