|
View previous topic :: :: View next topic
|
| Author |
Message |
DB2 Guy
New User
Joined: 28 Oct 2008
Posts: 98
Location: Cubicle
|
|
|
|
Hi,
I've got a weird requirement: for example there is this kind of a step executing REXEC:
| Code: |
//STEP015 EXEC PGM=REXEC, TIME=NOLIMIT,
// PARM='/-l abcdefg -p abc001 111.1.111.111 updInspct.pl INSPCT'
//SYSTCPD DD DSN=SYS1.TCPPARMS(TCPDATA),DISP=SHR
//SYSPRINT DD SYSOUT=* |
and I need to "hide" the PARM info, as in, it should not be visible to human eyes.
So to compete with this - I thought one solution might be using "parameterization". For example:
| Code: |
// JCLLIB ORDER=MY.OWN.JCLLIB
//*
// INCLUDE MEMBER=HIDEIT
//*
//STEP015 EXEC PGM=REXEC, TIME=NOLIMIT,
// PARM=&FPARM
//*
//SYSTCPD DD DSN=SYS1.TCPPARMS(TCPDATA),DISP=SHR
//SYSPRINT DD SYSOUT=*
//* |
the contents of HIDEIT
| Code: |
// SET PRM1=/
// SET PRM2=-
// SET FPARM='L ABCDEFG -P ABC001 111.1.111.111 UPDINSPCT.PL INSPCT' |
But on JCl-syntax chek, it give me two errors:
1. VALUE '/-L' MUST BE QUOTED OR IS QUOTED INCORRECTLY. I belive it's because "/" and "-" are not recognised by JCl cheker.
2. If I remove PRM1 and PRM2 and only passes rest of the value (FPARM) it works, BUT - only if the contents are in CAPS. Small case ae not being accepted as the valid JCL charcters.
Please assist.
I looked at REXEC manuals and it says the information via PARM is case sensitive, it has to be exacty same as needed. And as it is ID and paswword info - the chances of fighting back on the original requirements get slim...
can soeone please point to some work aorund... |
|
| Back to top |
|
 |
|
|
prino
Senior Member
Joined: 07 Feb 2009
Posts: 1103
Location: Oostende, Belgium
|
|
|
|
1) JCL check is not a substitute for the normal JCL conversion process.
| Code: |
// SET PRM1='/'
// SET PRM2='-' |
will work!
2) Lowercase is absolutely no problem in quoted SET statements or in the PARM=. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8317
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| I need to "hide" the PARM info, as in, it should not be visible to human eyes. |
You DO realize, I hope, that this "requirement" is bogus and cannot actually be achieved -- even if you by some miracle managed to hide this data in the source, it would be visible to anyone with access to the job queue? Furthermore, if you are attempting to hide the user id and password for the remote server, why are you not using the NETRC facility that IBM already provides for this purpose? If you don't know about NETRC, I recommend you find a copy of the Communications Server IP User's Guide manual and start reading. |
|
| Back to top |
|
|
David Robinson
Active User
Joined: 21 Dec 2011
Posts: 182
Location: UK
|
|
|
|
| Why don't you have the user ID and passord in a dataset which the Rexx routine reads instead of having it on the parm statement? |
|
| Back to top |
|
|
DB2 Guy
New User
Joined: 28 Oct 2008
Posts: 98
Location: Cubicle
|
|
|
|
Thanks Prino. Actually, I did a silly mistake of not using quotes around the symbolic &FPARM in JCL and your hint helped in here.
Thanks. |
|
| Back to top |
|
|
DB2 Guy
New User
Joined: 28 Oct 2008
Posts: 98
Location: Cubicle
|
|
|
|
Yes, Robert I do realize that and I tried to convenience the client but then not everyone is (technically) intelligent enough to think in that direction.
Thanks for the hint on NETRC. A nice 'reading-week' is ahead...
David - it's not REXX, it’s REmote eXECution - The REmote eXECution protocol (REXEC) is a remote execution client that lets you run a command on a remote host and receive the results on the local host. |
|
| Back to top |
|
|
David Robinson
Active User
Joined: 21 Dec 2011
Posts: 182
Location: UK
|
|
|
|
Whoops, sorry!  |
|
| Back to top |
|
|
|
