Re: Run a REXX from JCL stream

[Scott Ford]

Steve,

I usually do paragraph thru paragraph name-exit. Unfortunately I am also 
writing in C and Assemblerhard to remember which is which.

Scott ford
www.identityforge.com
from my IPAD

'Infinite wisdom through infinite means'


On Apr 30, 2013, at 4:23 PM, Steve Thompson  wrote:

> From:   John McKown 
> Date:   04/30/2013 11:19 AM
> 
> 
> 
> 
> 
> IF condition THEN
>  STATEMENT
> END-IF
> 
> and I usually only put a single period in a paragraph, as the last line in
> the paragraph. Everything else is delimited with END-verb. I never use 
> NEXT
> SENTENCE any more. 
> 
> 
> 
> What about END-PARAGRAPH?
> 
> 
> 
> Later,
> Steve Thompson
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Steve Thompson]

From:   John McKown 
Date:   04/30/2013 11:19 AM





IF condition THEN
  STATEMENT
END-IF

and I usually only put a single period in a paragraph, as the last line in
the paragraph. Everything else is delimited with END-verb. I never use 
NEXT
SENTENCE any more. 



What about END-PARAGRAPH?



Later,
Steve Thompson

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Scott Ford]

John,

I do to.otherwise it can be difficult to remember where your at in your code.

Scott ford
www.identityforge.com
from my IPAD

'Infinite wisdom through infinite means'


On Apr 30, 2013, at 11:07 AM, John McKown  wrote:

> Ah, a proto-manager! Too bad that there are quite a few COBAL (deliberate)
> programmers and so few COBOL. Or, like many, still stuck using the very old
> coding techniques. I am _finally_ seeing some COBOL which does in-line
> PERFORM statements. I see very little, other than that and IF, that use the
> END-verb constructs. Yes, it is a bit wordy. But I think it enhances
> comprehension. Just like in my C and Javascript code, I enclose statements
> in { } even when not absolutely necessary.
> 
> You can do:
> 
> for (int i=0;i 
> but I always code:
> 
> for (int i=o,i call function(i);
> }
> 
> I even code
> 
> IF condition THEN
>  STATEMENT
> END-IF
> 
> and I usually only put a single period in a paragraph, as the last line in
> the paragraph. Everything else is delimited with END-verb. I never use NEXT
> SENTENCE any more. 
> 
> On Tue, Apr 30, 2013 at 9:44 AM, Gerhard Postpischil 
> wrote:
> 
>> On 4/30/2013 10:27 AM, Farley, Peter x23353 wrote:
>> 
>>> Seriously, I think you denigrate application programmers with remarks
>>> like that.  We are not dumb coding robots with no experiences outside
>>> of our COBOL shell.
>> 
>> There are programmers who write CoBOL, and there are CoBOL programmers.
>> It's the latter we remember due to their uncanny ability to get into
>> trouble; it's human nature to rubber-neck at traffic accidents, too.
>> 
>> When I was a systems programmer at ADR, customer support had an
>> intractable problem - a user production job kept running out of memory
>> regardless of the region provided; the same job had run correctly during
>> testing in the default region. It was a simple CoBOL file processing
>> program with an E15 and E35 exit routine. When it was put into production,
>> it was added under the, to them, obvious name of SORT.
>> 
>> Nearly ten years later, at AMS, there was this user who kept running out
>> of space.
>> 
>> Gerhard Postpischil
>> Bradford, Vermont
>> 
>> 
>> --**--**--
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> 
> 
> -- 
> This is a test of the Emergency Broadcast System. If this had been an
> actual emergency, do you really think we'd stick around to tell you?
> 
> Maranatha! <><
> John McKown
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[John McKown]

Ah, a proto-manager! Too bad that there are quite a few COBAL (deliberate)
programmers and so few COBOL. Or, like many, still stuck using the very old
coding techniques. I am _finally_ seeing some COBOL which does in-line
PERFORM statements. I see very little, other than that and IF, that use the
END-verb constructs. Yes, it is a bit wordy. But I think it enhances
comprehension. Just like in my C and Javascript code, I enclose statements
in { } even when not absolutely necessary.

You can do:

for (int i=0;i

On Tue, Apr 30, 2013 at 9:44 AM, Gerhard Postpischil wrote:

> On 4/30/2013 10:27 AM, Farley, Peter x23353 wrote:
>
>> Seriously, I think you denigrate application programmers with remarks
>> like that.  We are not dumb coding robots with no experiences outside
>> of our COBOL shell.
>>
>
> There are programmers who write CoBOL, and there are CoBOL programmers.
> It's the latter we remember due to their uncanny ability to get into
> trouble; it's human nature to rubber-neck at traffic accidents, too.
>
> When I was a systems programmer at ADR, customer support had an
> intractable problem - a user production job kept running out of memory
> regardless of the region provided; the same job had run correctly during
> testing in the default region. It was a simple CoBOL file processing
> program with an E15 and E35 exit routine. When it was put into production,
> it was added under the, to them, obvious name of SORT.
>
> Nearly ten years later, at AMS, there was this user who kept running out
> of space.
>
> Gerhard Postpischil
> Bradford, Vermont
>
>
> --**--**--
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
This is a test of the Emergency Broadcast System. If this had been an
actual emergency, do you really think we'd stick around to tell you?

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[John Gilmore]

The skill levels of COBOL programmers vary enormously.  The best are
very good indeed, but most of them begin better than they end because
the shops where they work do not prize programming skills.

They instead prize something called "knowing the business", which too
often turns out to be detailed, anecdotal knowledge of how some badly
designed application functions after 15 years of ill-considered
maintenance.

If I were apportioning blame for this situation I should blame IT
management rather than these programmers; but to say this is not to
say that any large number of COBOL programmers are, qua programmer,
very good at what they do.

John Gilmore, Ashland, MA 01721 - USA

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Gerhard Postpischil]

On 4/30/2013 10:27 AM, Farley, Peter x23353 wrote:

Seriously, I think you denigrate application programmers with remarks
like that.  We are not dumb coding robots with no experiences outside
of our COBOL shell.


There are programmers who write CoBOL, and there are CoBOL programmers. 
It's the latter we remember due to their uncanny ability to get into 
trouble; it's human nature to rubber-neck at traffic accidents, too.


When I was a systems programmer at ADR, customer support had an 
intractable problem - a user production job kept running out of memory 
regardless of the region provided; the same job had run correctly during 
testing in the default region. It was a simple CoBOL file processing 
program with an E15 and E35 exit routine. When it was put into 
production, it was added under the, to them, obvious name of SORT.


Nearly ten years later, at AMS, there was this user who kept running out 
of space.


Gerhard Postpischil
Bradford, Vermont

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Farley, Peter x23353]

Hey!  I resemble that remark!

Seriously, I think you denigrate application programmers with remarks like 
that.  We are not dumb coding robots with no experiences outside of our COBOL 
shell.

*Some* of us are even experts in assembler as well as COBOL as well as C as 
well as linux tool chains as well as ...  You get the picture.

TIA for not putting us down in public quite so baldly.

Peter

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Graham Hobbs
Sent: Monday, April 29, 2013 10:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Run a REXX from JCL stream

At a guess, how many COBOL/CICS developers have ever heard of IKJEFT01? 
Start your count at 2.
--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Thomas Conley]

On 4/30/2013 8:45 AM, Paul Gilmartin wrote:

On Tue, 30 Apr 2013 14:27:28 +0200, Hunkeler Peter (TLSG 4) wrote:


To run a REXX from any sequential data set, code:
EX 'your.rexx.ps.data.set'

And to be complete, to run a REXX from any member in any PDS (not
necessarily allocated to //SYSEXEC or //SYSPROC), code:
  EX 'your.rexx.pds.data.set(member)'


Well, not entirely complete.  Neither of these techniques suffices to run
a REXX residing in a z/OS UNIX file.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



Use BPXBIATCH to run USS Rexx execs in batch.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Shmuel Metz (Seymour J.)]

In <0DA8183E177E484CA79B421C02D26788@graham>, on 04/29/2013
   at 10:06 PM, Graham Hobbs  said:

>At a guess, how many COBOL/CICS developers have ever heard of
>IKJEFT01? 

At a guess, 10,000.

-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 Atid/2
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Hunkeler Peter (TLSG 4)]

>Well, not entirely complete. 

Which one(s) was I missing?

--
Peter Hunkeler

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Paul Gilmartin]

On Tue, 30 Apr 2013 14:27:28 +0200, Hunkeler Peter (TLSG 4) wrote:
>
>To run a REXX from any sequential data set, code:
>EX 'your.rexx.ps.data.set'
>
>And to be complete, to run a REXX from any member in any PDS (not
>necessarily allocated to //SYSEXEC or //SYSPROC), code:
>  EX 'your.rexx.pds.data.set(member)'
> 
Well, not entirely complete.  Neither of these techniques suffices to run
a REXX residing in a z/OS UNIX file.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Hunkeler Peter (TLSG 4)]

>REXX programs cannot be written inline. You must save it in a PDS. You
then
>allocate that PDS to either SYSPROC or SYSEXEC.

Just in case someone ever finds this in the archive: "must" is a bit too
strict.

It is quite usual but not necessary to store REXX programs a members  in
a *PDS*. A REXX program can well be run from a simple sequential data
set. 
What changes is that you cannot use the "%" syntax to run it. "%FOO"
searches //SYSEXEC, then //SYSPROC for a member with that name.

To run a REXX from any sequential data set, code:
EX 'your.rexx.ps.data.set'

And to be complete, to run a REXX from any member in any PDS (not
necessarily allocated to //SYSEXEC or //SYSPROC), code:
  EX 'your.rexx.pds.data.set(member)'

--
Peter Hunkeler

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Graham Hobbs]

At a guess, how many COBOL/CICS developers have ever heard of IKJEFT01? 
Start your count at 2.


- Original Message - 
From: "Shmuel Metz (Seymour J.)" 

Newsgroups: bit.listserv.ibm-main
To: 
Sent: Monday, April 29, 2013 9:54 PM
Subject: Re: Run a REXX from JCL stream



In , on 04/27/2013
  at 08:27 PM, Graham Hobbs  said:


Subject: Run a REXX from JCL stream


That's not how IKJEFT011 works.


Am a 'not a sysprog'


You don't need to be an SP to use IKJEFT01.


//SYSTSIN  DD DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR


That has to be TSO commands and prompt data for commands, not REXX
code. Put your foo REXX in SYSEXEC and call it with %foo.

--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Atid/2<http://patriot.net/~shmuel>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Shmuel Metz (Seymour J.)]

In , on 04/27/2013
   at 08:27 PM, Graham Hobbs  said:

>Subject: Run a REXX from JCL stream

That's not how IKJEFT011 works.

>Am a 'not a sysprog' 

You don't need to be an SP to use IKJEFT01.

>//SYSTSIN  DD DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR

That has to be TSO commands and prompt data for commands, not REXX
code. Put your foo REXX in SYSEXEC and call it with %foo.

-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 Atid/2<http://patriot.net/~shmuel>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Terry Sambrooks]

Hi Graham,

Despite being Sunday and knowing that you already have a solution I thought
I would add the following to demonstrate that if there is a need to run REXX
inline, it can be done within a single step and using a sequential data set
to hold the rexx code if it is remembered that IDCAMS commands can be driven
directly from TSO, as in:

//ADCDMSTB JOB  CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID 
//S0010EXEC PGM=IKJEFT01  
//SYSTSPRT DD   SYSOUT=*  
//SYSEXEC  DD   UNIT=SYSDA,SPACE=(80,(100,50)),AVGREC=U,LRECL=80, 
// BLKSIZE=27920,RECFM=FB,DSN=ADCDMST.SEQ.REXX,   
// DISP=(,DELETE) 
//SYSTSIN  DD   * 
 REPRO INFILE(REXXCODE),OUTFILE(SYSEXEC)  
EXEC 'ADCDMST.SEQ.REXX' EXEC  
//REXXCODE DD *,DLM='?@'  
/* REXX batch inline demo */  
Say 'Welcome to REXX' 
Exit 0
?@

Kind Regards - Terry
 
Director
KMS-IT Limited
228 Abbeydale Road South
Dore
Sheffield
S17 3LA
UK
 
Reg : 3767263
 
Outgoing e-mails have been scanned, but it is the recipients responsibility
to ensure their anti-virus software is up to date.
 
 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Leonardo Vaz]

Here is what I do to have the rexx instream and run it:

//CREATREX  EXEC PGM=IEBGENER
//SYSPRINT  DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT2   DD  DSN=&&PDS(REXX),UNIT=SYSALLDA,
// DISP=(NEW,PASS,DELETE),
// SPACE=(TRK,(1,1,1)),
// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB,DSORG=PO)
//SYSUT1DD DATA,DLM=##
/* rexx here */
##
//EXECREXX EXEC PGM=IKJEFT01,PARM='REXX',REGION=0M
//SYSTSIN  DD  DUMMY
//SYSTSPRT DD  SYSOUT=*
//SYSEXEC  DD  DSN=&&PDS,DISP=(OLD,DELETE,DELETE)

Regards,
Leo

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Saturday, April 27, 2013 9:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Run a REXX from JCL stream

On Sat, 27 Apr 2013 19:49:23 -0500, John McKown wrote:

>REXX programs cannot be written inline. ...
> 
Perhaps.  There may be an undocumented, probably unintended, certainly 
unsupported back door: it has been reported that if you invoke IRXJCL supplying 
binary zeroes in PARM as a member name, the interpreter perceives SYSEXEC as a 
sequential data set and executes it as such.

I don't recall whether I've tried it.  I wouldn't rely on it.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Paul Gilmartin]

On Sat, 27 Apr 2013 19:49:23 -0500, John McKown wrote:

>REXX programs cannot be written inline. ...
> 
Perhaps.  There may be an undocumented, probably unintended,
certainly unsupported back door: it has been reported that if you
invoke IRXJCL supplying binary zeroes in PARM as a member name,
the interpreter perceives SYSEXEC as a sequential data set and
executes it as such.

I don't recall whether I've tried it.  I wouldn't rely on it.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Graham Hobbs]

Gentlemen,
Despite the fact that it's Saturday evening, latish, thirty minutes after 
posting:-), I got the perfect answers. Works a treat.

Can't thankyou enough,
Graham

- Original Message - 
From: "Hardee, Chuck" 

Newsgroups: bit.listserv.ibm-main
To: 
Sent: Saturday, April 27, 2013 8:52 PM
Subject: Re: Run a REXX from JCL stream


Graham,

Try this:

//ATEST   JOB (CONRAD-B),'IBMUSE2',
// CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1)
//JOBLIB   DD DSN=VENDOR.LINKLIB.SECOND,DISP=SHR
//*--
//STEPNAME  EXEC PGM=IKJEFT01
//SYSEXEC  DD DSN=VENDOR.SYSEXEC,DISP=SHR<= JOB2 will be 
retrieved and executed from here

//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
JOB2
/*


Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Services
Thermo Fisher Scientific
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
chuck.har...@thermofisher.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
Behalf Of Graham Hobbs

Sent: Saturday, April 27, 2013 8:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Run a REXX from JCL stream

Hello,
Am a 'not a sysprog' doing stuff at Dallas IIC under z/OS. Another prob (for 
me anyway). Have a JCL stream, first step is supposed to run a REXX pgm but 
it won't. Googling didn't help. Can anybody tell me what I've missed.


JCL I sub is:
//ATEST   JOB (CONRAD-B),'IBMUSE2',
// CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1)
//JOBLIB   DD DSN=VENDOR.LINKLIB.SECOND,DISP=SHR
//*--
//STEPNAME  EXEC PGM=IKJEFT01
//SYSEXEC  DD DSN=VENDOR.SYSEXEC,DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR
.. followed by other stuff.

REXX is:
/* rexx */
  say 'Job1 started'
  say 'Job1 ended'
  exit

Result in SDSF;O is:
* TOP OF DATA ***
READY
/* rexx */
READY
  say 'Job1 started'
IKJ56500I COMMAND SAY NOT FOUND
READY
  say 'Job1 ended'
IKJ56500I COMMAND SAY NOT FOUND
READY
  exit
IKJ56500I COMMAND EXIT NOT FOUND
READY
END
 BOTTOM OF DATA *

Looking at the output 'it' certainly found the REXX - that's a start - 
success ended there!  Also IKJ56500 isn't in the manual and googling didn't 
help.

Please, thanks,
Graham Hobbs

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Hardee, Chuck]

Graham,

Try this:

//ATEST   JOB (CONRAD-B),'IBMUSE2',  
// CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1) 
//JOBLIB   DD DSN=VENDOR.LINKLIB.SECOND,DISP=SHR 
//*--
//STEPNAME  EXEC PGM=IKJEFT01
//SYSEXEC  DD DSN=VENDOR.SYSEXEC,DISP=SHR<= JOB2 will be retrieved 
and executed from here
//SYSTSPRT DD SYSOUT=*   
//SYSTSIN  DD *
 JOB2 
/*


Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Services
Thermo Fisher Scientific
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
chuck.har...@thermofisher.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Graham Hobbs
Sent: Saturday, April 27, 2013 8:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Run a REXX from JCL stream

Hello,
Am a 'not a sysprog' doing stuff at Dallas IIC under z/OS. Another prob (for me 
anyway). Have a JCL stream, first step is supposed to run a REXX pgm but it 
won't. Googling didn't help. Can anybody tell me what I've missed.

JCL I sub is:
//ATEST   JOB (CONRAD-B),'IBMUSE2',  
// CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1) 
//JOBLIB   DD DSN=VENDOR.LINKLIB.SECOND,DISP=SHR 
//*--
//STEPNAME  EXEC PGM=IKJEFT01
//SYSEXEC  DD DSN=VENDOR.SYSEXEC,DISP=SHR
//SYSTSPRT DD SYSOUT=*   
//SYSTSIN  DD DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR
.. followed by other stuff.

REXX is:
/* rexx */ 
   say 'Job1 started'  
   say 'Job1 ended'
   exit

Result in SDSF;O is:
* TOP OF DATA ***
READY
/* rexx */   
READY
   say 'Job1 started'
IKJ56500I COMMAND SAY NOT FOUND  
READY
   say 'Job1 ended'  
IKJ56500I COMMAND SAY NOT FOUND  
READY
   exit  
IKJ56500I COMMAND EXIT NOT FOUND 
READY
END  
 BOTTOM OF DATA *

Looking at the output 'it' certainly found the REXX - that's a start - success 
ended there!  Also IKJ56500 isn't in the manual and googling didn't help. 
Please, thanks,
Graham Hobbs

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[Gerhard Postpischil]

On 4/27/2013 8:27 PM, Graham Hobbs wrote:

Hello, Am a 'not a sysprog' doing stuff at Dallas IIC under z/OS.
Another prob (for me anyway). Have a JCL stream, first step is
supposed to run a REXX pgm but it won't. Googling didn't help. Can
anybody tell me what I've missed.

JCL I sub is: //ATEST   JOB (CONRAD-B),'IBMUSE2', //
CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1) //JOBLIB   DD
DSN=VENDOR.LINKLIB.SECOND,DISP=SHR //*--
//STEPNAME  EXEC PGM=IKJEFT01 //SYSEXEC  DD
DSN=VENDOR.SYSEXEC,DISP=SHR //SYSTSPRT DD SYSOUT=* //SYSTSIN  DD
DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR .. followed by other stuff.

REXX is: /* rexx */ say 'Job1 started' say 'Job1 ended' exit


The JCL you are using is suitable only for executing commands, not 
individual REXX statements (which is why your /* REXX */ was ignored). 
The simplest way is to run an IEBGENER to copy your REXX code to a PDS 
(temporary or other), using a member name under which you'll invoke that 
code. Concatenate that PDS as part of your SYSEXEC DD; make sure that 
you use matching DCB parameters for all SYSEXEC files.


It is also possible to invoke REXX directly (interpreter or compiler, 
depending on what your installation is licensed for), but then you won't 
have the TSO, ISP or ISR environments.


Gerhard Postpischil
Bradford, Vermont

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Run a REXX from JCL stream

[John McKown]

REXX programs cannot be written inline. You must save it in a PDS. You then
allocate that PDS to either SYSPROC or SYSEXEC. You can then run it like:

//REXX EXEC PGM=IKJEFT01
//SYSECEC DD DISP=SHR,DSN=PDS.containing.REXX.pgm
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%rexxpgm
/*
//

Where "rexxpgm" is the PDS member name in the PDS.
 On Apr 27, 2013 7:27 PM, "Graham Hobbs"  wrote:

> Hello,
> Am a 'not a sysprog' doing stuff at Dallas IIC under z/OS. Another prob
> (for me anyway). Have a JCL stream, first step is supposed to run a REXX
> pgm but it won't. Googling didn't help. Can anybody tell me what I've
> missed.
>
> JCL I sub is:
> //ATEST   JOB (CONRAD-B),'IBMUSE2',
> // CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1)
> //JOBLIB   DD DSN=VENDOR.LINKLIB.SECOND,DISP=SHR
> //*--
> //STEPNAME  EXEC PGM=IKJEFT01
> //SYSEXEC  DD DSN=VENDOR.SYSEXEC,DISP=SHR
> //SYSTSPRT DD SYSOUT=*
> //SYSTSIN  DD DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR
> .. followed by other stuff.
>
> REXX is:
> /* rexx */
>say 'Job1 started'
>say 'Job1 ended'
>exit
>
> Result in SDSF;O is:
> * TOP OF DATA ***
> READY
> /* rexx */
> READY
>say 'Job1 started'
> IKJ56500I COMMAND SAY NOT FOUND
> READY
>say 'Job1 ended'
> IKJ56500I COMMAND SAY NOT FOUND
> READY
>exit
> IKJ56500I COMMAND EXIT NOT FOUND
> READY
> END
>  BOTTOM OF DATA *
>
> Looking at the output 'it' certainly found the REXX - that's a start -
> success ended there!  Also IKJ56500 isn't in the manual and googling didn't
> help.
> Please, thanks,
> Graham Hobbs
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Run a REXX from JCL stream

[Graham Hobbs]

Hello,
Am a 'not a sysprog' doing stuff at Dallas IIC under z/OS. Another prob (for me 
anyway). Have a JCL stream, first step is supposed to run a REXX pgm but it 
won't. Googling didn't help. Can anybody tell me what I've missed.

JCL I sub is:
//ATEST   JOB (CONRAD-B),'IBMUSE2',  
// CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1) 
//JOBLIB   DD DSN=VENDOR.LINKLIB.SECOND,DISP=SHR 
//*--
//STEPNAME  EXEC PGM=IKJEFT01
//SYSEXEC  DD DSN=VENDOR.SYSEXEC,DISP=SHR
//SYSTSPRT DD SYSOUT=*   
//SYSTSIN  DD DSN=VENDOR.SYSEXEC(JOB2),DISP=SHR
.. followed by other stuff.

REXX is:
/* rexx */ 
   say 'Job1 started'  
   say 'Job1 ended'
   exit

Result in SDSF;O is:
* TOP OF DATA ***
READY
/* rexx */   
READY
   say 'Job1 started'
IKJ56500I COMMAND SAY NOT FOUND  
READY
   say 'Job1 ended'  
IKJ56500I COMMAND SAY NOT FOUND  
READY
   exit  
IKJ56500I COMMAND EXIT NOT FOUND 
READY
END  
 BOTTOM OF DATA *

Looking at the output 'it' certainly found the REXX - that's a start - success 
ended there!  Also IKJ56500 isn't in the manual and googling didn't help. 
Please, thanks,
Graham Hobbs

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN