Result:
If 'JOB' is typed in command line in the jcl being edited, I get a jobcard as below
//X11421A JOB (R004,FIB),11421AB,CLASS=Z,MSGCLASS=X,
// REGION=2048K,MSGLEVEL=(1,1),NOTIFY=X11421
If 'JOB Y' is typed in command line in the jcl being edited, I get a jobcard as below
//X11421A JOB (R004,FIB),11421AB,CLASS=Z,MSGCLASS=X,
// REGION=2048K,MSGLEVEL=(1,1),NOTIFY=X11421
/*JOBPARM ROOM=OVER,S=019E
I require a Jobcard as below
//X11421A JOB (R004,FIB),'11421AB',CLASS=Z,MSGCLASS=X,
// REGION=2048K,MSGLEVEL=(1,1),NOTIFY=X11421
/*JOBPARM ROOM=OVER,S=019E
Single quotes around Programmer id (11421AB) is required. If I modify the code as follows
I get an error,
----------------
Command in error . : ISREDIT LINE_AFTER 0 = DATALINE '//X11421A JOB (R00
Incomplete string
Put an ending quote at the end of the string.
Error message ID . : ISRE060
Last return code . : 20
Macro executing . : JOB
Press ENTER key to terminate the macro.
---------------
same with double single quotes,
MSG = "'//"UID"A JOB (R004,FIB),''"PID"'',CLASS=Z,MSGCLASS=X,'"
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
to get around these kind of problems,
i always maintain a skeleton PDS,
each member has a function.
one is a jobcard
one is parms to load for this or that.
i just do a straight copy of the skel into the current dataset,
(before .zf)
and since I know what the member (that I just copied)
looks like, i make the necessary chgs.
Joined: 01 Sep 2006 Posts: 2547 Location: Silicon Valley
The problem is that:
1. quotes are rexx delimiters
2. quotes are macro statement delimiters
3. you want quotes in your result
In such cases, I use a different character instead of the quote character, such as '~', which is not likely to be used in the file. Then in a final step, change all "~" to "'".
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
maheshk84 wrote:
Thanks dbzTHEdinosauer for your reply but I was feeling lazy to create skels for this simple requirement. I will try as you mentioned when I get time.
i missused the term skeleton. I did not mean ispf skeletons,
just a member (or dataset) containing what I wanted the jcl to look like,
simple copy and change the required.