IBM Mainframe Forum

by **gokulNmf** » Tue Oct 04, 2011 7:12 pm

Hi All,
I am running a rexx pgm in batch mode using the utility Ikjeft1a (Please find the code below), the issue is the rexx pgm needs the input, which is 80 bytes long. can anyone help me how to continue the input in the next line.

i tired : -, comma, spaces,
( xxxx -
xxx),
' xxxxx
xxxx'
none was working.

HELLO - rexx pgm
XXXXXXXXXXX- is the input to the rexx
GARUL.COMPARE.ICETOOL.FILE1 - is the input file.

Select all

//TSOBATCH EXEC PGM=IKJEFT1A
//SYSEXEC DD DSN=GARUL.PRICING.REXXLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//INFILE01 DD DSN=GARUL.COMPARE.ICETOOL.FILE1,DISP=SHR
//SYSTSIN DD *
%HELLO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
//*

by **MrSpock** » Tue Oct 04, 2011 7:48 pm

I pulled this from the TSO/E User's Guide:

SYSTSIN DD Statement

The SYSTSIN DD statement is used to specify that the data to follow consists of executable commands and/or subcommands. For example, to indicate to the system that all data following this statement is to be used as input, until the system encounters an input delimiter, such as the characters /* or the DLM operand, specify:

//SYSTSIN DD *If any of the input statements start with the characters //, use the DD DATA statement instead.

To indicate to the system that all data following this statement is to be used as input, including statements that start with the characters //, until an input delimiter (/* or DLM) is found, specify:

//SYSTSIN DD DATATo indicate to the system that all the input data can be found in data set PREFIX.INPUT.DATA, specify:

//SYSTSIN DD DSNAME=PREFIX.INPUT.DATAThe SYSTSIN and SYSTSPRT DD statements can refer to a sequential data set or a member of a partitioned data set.
It is recommended that the SYSTSIN DD be defined as a fixed block format data set, with an LRECL of 80.

If SYSTSIN is a fixed length data set (FB), the last 8 bytes of the record will be treated as a sequence number and ignored.

If SYSTSIN is a fixed length data set with ASA control characters (FBA), the first byte of the record will be treated as a carriage control character and ignored.

If SYSTSIN is a variable length data set (VB), the first 8 bytes of the record will be treated as a sequence number and ignored.

If SYSTSIN is a variable length data set with ASA control characters (VBA), the first 9 bytes of the record will be treated as a sequence number, followed by a carriage control character and ignored.

You cannot refer to concatenated data sets on the SYSTSIN DD statement. Each command or subcommand must begin on a separate statement.

So, apparently the longest single record if your SYSTSIN is allocated as RECFM=FB, LRECL=80, will be 72 characters. I'd say either go with a larger allocation (instream data can be up to 254 characters), pass the data as PARM= instead of using SYSTSIN, or logically break it up into two records.

by **steve-myers** » Wed Oct 05, 2011 12:29 am

There are two parts to this topic: a Rexx question about the mechanics of reading an input dataset with multiple records, and how to provide a logical input record to TSO that is longer than 73 or 80 bytes. I won't respond to the Rexx question as I don't write very much Rexx, but I can respond to the TSO input question.

It's pretty much forgotten now, but I'm sure it's discussed in the TSO/E User's Guide that you can provide very long input lines by terminating a logical input line with a - or + character and continue the logical line on the next input line. I believe there is a maximum length, but I've never encountered it. Like so -

Select all

//A EXEC PGM=IKJEFT1A
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
LISTD ('SYS1.LINKLIB' 'SYS1.LPALIB' -
'SYS1.SVCLIB' 'SYS1.PROCLIB')
/*

I just ran that today, and it ran fine. There is a difference between using the - or + character that you can find out yourself in the TSO/E User's Guide.

by **Akatsukami** » Wed Oct 05, 2011 2:24 am

Would not be wiser, in this case, to read the data from SYSIN, rather than trying to get it (presumably as a parameter) from SYSTSIN?

by **gokulNmf** » Thu Oct 13, 2011 7:21 pm

@ Akatsukami: i am not aware of that :oops:

, can you please let me know where can i find more info of, getting input through sysin instead of systsin?

@steve-myers & MrSpock: Thank you, i made it by passing the input through a DS with required length.

by **NicC** » Thu Oct 13, 2011 7:29 pm

SYSIN is just another DDname to your program - you used a different DDname, that is all

by **gokulNmf** » Fri Oct 14, 2011 11:32 am

Hey NicC,
Thanks for the reply, i would like to know how to give the SYSTSIN parameters through SYSIN as input?. The confusion i am having is: the utitly will check the systsin or sysin for the input?

by **enrico-sorichetti** » Fri Oct 14, 2011 11:41 am

it seemed to me that MsSpock quote was enlightening enough

IKJEFT01 and friends ( IKJEFT1x ) is NOT an utility
it is the TMP aka TERMINAL MONITOR PROGRAM...
it sits there doing nothing until a recognized TSO <command> is entered/read
as such the only data it knows about are the <command> strings,

the ONLY ddnames needed are
SYSTSIN for the command and all the related parameters
and SYSTSPRT for the command related output

it is recommended to read any other data thru a different DDNAME

All You might want to know about IKJEFT01 can be easily found here
http://publibz.boulder.ibm.com/cgi-bin/ ... s/IKJ4BK90
not the latest one but more than enough as an introductory reading

by **steve-myers** » Fri Oct 14, 2011 9:40 pm

gokulNmf wrote:Hey NicC,
Thanks for the reply, i would like to know how to give the SYSTSIN parameters through SYSIN as input?. The confusion i am having is: the utitly will check the systsin or sysin for the input?

IKJEFT01 and it's friends are the TSO Terminal Monitor Program. When it is called in a batch job it reads its commands only from the dataset specified by the DD statement with DD name SYSTSIN and writes line mode terminal output to the dataset specified by the DD statement with the SYSTSPRT DD name. There are no alternatives. What I thnk you want to do can't be done firectly, though you can play JCL games. i haven't tried this, but I think it will word.

Select all

//A EXEC PGM=IKJEFT1A
//SYSTSPRT DD DDNAME=SYSPRINT
//SYSTSIN DD DDNAME=SYSIN
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
LISTD 'SYS1.LINKLIB' ME

by **Akatsukami** » Fri Oct 14, 2011 10:12 pm

gokulNmf wrote:@ Akatsukami: i am not aware of that , can you please let me know where can i find more info of, getting input through sysin instead of systsin?

Sorry to have left you hanging; occasionally my managers expect me to justify my salary by doing some actural work.

SYSIN can be treated just like any other file, and read with EXECIO or a third-party package (we have such a package here, but never bother with it for PS data sets, as it gives no advantage over EXECIO unless we have to run in a non-TSO address space). A very simple exec that just echoes its input:

Select all

/* Rexx */
/* Written Heisei 23.10.14 by Akatsukami-sama */
trace o
"EXECIO 1 DISKR SYSIN"

do while (rc=0)
parse pull line
say "I say unto you:" line
"EXECIO 1 DISKR SYSIN"
end

The JCL to run it:

Select all

//STEPONLY EXEC PGM=IKJEFT1B
//SYSPROC DD DSN=SHGB.WORK.CLIST,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%FOO57
//SYSIN DD *
i tired : -, comma, spaces,
( xxxx -
xxx),
' xxxxx
xxxx'
none was working.

And the SYSTSPRT output:

Select all

1READY
%FOO57
I say unto you: i tired : -, comma, spaces,
I say unto you: ( xxxx -
I say unto you: xxx),
I say unto you: ' xxxxx
I say unto you: xxxx'
I say unto you: none was working.
READY
END

IBM Mainframe Forum

IKJEFT1A utility help needed

IKJEFT1A utility help needed

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.

Re: Ikjeft1a utility help needed.