×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 10-Sep-2014 09:51 -0500, Laine, Rogers wrote:
I would like to define a physical file(CRTPF) with 80 byte records
RCDLEN(80) size then edit the file to define the JCL statements.
Once I create the file what method do I use to add the JCL
statements.
I have tried STRSEU and STRPDM without much success.
Once I have the JCL in the file I plan on doing FTP using....
FTP RMTSYS('1.2.3.4')
BIN
LCD SYSTEMS
SITE FILETYPE=JES
PUT JCLFILE
QUIT
The above worked but failed because the file was over 80 bytes and
the job on JES failed.
Others have mentioned Edit File (EDTF), but each failed to mention
specifically that the FILE() parameter should be used versus the STMF()
parameter to name\identify the member; the editor honors the Fixed
Length Record concept only when the member is identified using the
FILE() and MBR() parameters, else the data typed into the editor is
treated as a text stream with record delimiters.
FWiW: since the S/38, the typical way to edit purely text data in a
flat file was to use the SEU against a source physical file member with
the text data, and then copy the source into the undescribed file using
the Copy File (CPYF) utility. The Format Option (FMTOPT) parameter of
CPYF has a Convert Between Source And Data special value *CVTSRC that
allows copying the text data between a source PFM and a data PFM; e.g.
CPYF PFSRC_RL92 PFDTA_RL80 FMTOPT(*CVTSRC) /* given CRTSRCPF PFSRC_RL92
RCDLEN(92) and CRTPF PFDTA_RL80; the FROMFILE() and TOFILE() can be
reversed */
However both of the above might be moot, as likely the data can be
stored and edited as a SRC-PFM and then sent\transferred via FTP just as
if a RCDLEN(80) data file; i.e. the FTP should send only the SRCDTA
information, which is the 80-byte portion, omitting the SRCDAT and
SRCSEQ data in the copy of data transmitted.
IIRC: In the FTP client, be sure to specify BLOCK [MODE] and EBCDIC
[TYPE] to override the STREAM and ASCII defaults; ¿perhaps also RECORD
vs FILE [STRUCT]?. Also verify the LOCSITE TRIM option, to be sure the
setting is desirable.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.