MVSFORUMS.com

Phantom · Posted: Thu Jul 08, 2004 10:38 am Post subject:

Kolusu,

Our shop currently does not have QW. The licence has expired and they haven't renewed the licence yet. (Don't know when that wud happen) Could you please some documentation.

Thanks a bunch,
Phantom,

kolusu · Posted: Thu Jul 08, 2004 10:40 am Post subject:

Phantom,

Check this link

http://www.mvsforums.com/helpboards/viewtopic.php?t=2520

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

superk · Advanced Joined: 19 Dec 2002 Posts: 684 Topics: 5

The invocation of REXX from COBOL is rather simple:

Cogito-Ergo-Sum · Posted: Thu Jul 08, 2004 1:53 pm Post subject:

Kevin,
I like the solution. I was led into thinking of calling REXX EXEC load module rather than having invoking it via IRXJCL.

However, the way of calling IRXJCL is not correct. You are calling the program by its name; meaning it is statically called. In other words, it must be available in the load module of PROG6.

When I tested your code, sure enough, the link step failed. It said, IRXJCL symbol is unresolved. However, it works perfectly, when I call it via an identifier.

Here is what worked for me:

Cogito-Ergo-Sum · Posted: Thu Jul 08, 2004 1:58 pm Post subject:

BTW, Kevin's job would also need a DD name SYSTSPRT where the 'say' of REXX would be printed. Else, the job will abend at run-time.
_________________
ALL opinions are welcome.

Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.

superk · Advanced Joined: 19 Dec 2002 Posts: 684 Topics: 5

You are correct about also needing SYSTSPRT.

I was just working on a version of this that uses BPXWDYN to dynamically allocate the SYSEXEC and SYSTSPRT DD's. Looks good thus far.

Cogito-Ergo-Sum · Posted: Thu Jul 08, 2004 4:07 pm Post subject:

And, about calling IRXJCL ?
_________________
ALL opinions are welcome.

Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.

superk · Advanced Joined: 19 Dec 2002 Posts: 684 Topics: 5

Well, the code compiled and executed just fine the way I originally posted it. However, what you said makes sense, using a dynamic call rather than a static call. I'll make the change tomorrow.

semigeezer · Posted: Fri Jul 09, 2004 1:32 am Post subject:

Calling a Rexx program in the name of 'security' will only get you into trouble.

It is easy to browse any load module that can be loaded into storage. DDLIST;LOAD module is the easiest, but there are many others including causing it to abend and looking at the dump, etc., etc.
Once you browse the load module, you can view the strings in it, so unless you encrypt the name, it wll be plainly visible.
If the user changes their SYSEXEC/SYSPROC concatenations, your Rexx exec can be substituted with a similarly named one that does whatever the user wants unless you call EXEC with a fully qualified name.
If the user frees the ddnames, they may get error messages telling them what commands could not be found.
... it s just too easy to get around.

It is possible to preload and preparse an exec in storage and call that via the IRX... interfaces. It is documented in the Rexx books, but
dynamic allocation (SVC 99, BPXWDYN, etc) of a temporary data set (leave off the dsname) is probably your best bet. All the better if it is allocated to VIO. RACF can provide some additional safeguards like execute-only authority.

Phantom · Posted: Fri Jul 09, 2004 1:37 am Post subject:

Wow, this is absolutely great. I'm learning lot of new things !!!! Thanks a lot for all of you Very Happy

Superk said

Phantom · Posted: Fri Jul 09, 2004 9:59 am Post subject:

Hi All,

I wrote a COBOL program that calls BPXWPDYN. I was able to successfully create a DATASET (PS), Open it in OUTPUT mode, write some data, close it & Free the allocated dataset. Everything worked fine !!!.

The only problem was I was trying to allocate a DDNAME to SYSOUT=* using the following command but ended with an error.

Cogito-Ergo-Sum · Posted: Fri Jul 09, 2004 10:28 am Post subject:

Check this:

ftp://ftp.software.ibm.com/s390/zos/tools/bpxwdyn/bpxwdyn.html#Section_2.3

for return codes.
_________________
ALL opinions are welcome.

Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.

Phantom · Posted: Fri Jul 09, 2004 10:32 am Post subject:

Cogito,

Our shop has a firewall that does not allow us to browse FTP sites. Could you please post the return codes in your message itself. That wud of great help to me.

Also, please let me know whether the syntax I used for allocating to SYSOUT=* was right. ( I used three different commands, but none of them worked). Please guide me,

Thanks,

Cogito-Ergo-Sum · Posted: Fri Jul 09, 2004 10:46 am Post subject:

Try

Phantom · Posted: Mon Jul 12, 2004 8:46 am Post subject:

Hi All,

Thanks a lot for all you help.

I Still have some problems directing a output file to SYSOUT=*. The Syntax provided in the BPXWDYN documentation didn't work for me. I'm not sure whether I made any mistake. Please guide me.

Syntax: