Re: Tips for continuing DD statement with only one parameter field
In 0818533857960322.wa.paulgboulderaim@bama.ua.edu, on 03/09/2012 at 08:32 AM, Paul Gilmartin paulgboul...@aim.com said: How would that affect the syntax or semantics of the DD PATH= parameter? A leading // would not be equivalent to a leading /. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
In d29926db-e688-4804-b15c-f4c166928...@yahoo.com, on 03/08/2012 at 12:01 PM, Scott Ford scott_j_f...@yahoo.com said: You saying the working directory on Z/os unix is different than the homes? I believe that he is saying that the working directopry on z/OS Unix need not be the same as the user's home directory, just as the TSO PROFILE PREFIX need not be the same as the user's userid. If that is what he is saying, it is correct. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
In 8073223666064012.wa.paulgboulderaim@bama.ua.edu, on 03/08/2012 at 09:45 AM, Paul Gilmartin paulgboul...@aim.com said: All DCB subparameters, or only some? Only some, but the most common. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
In 7326129770207562.wa.paulgboulderaim@bama.ua.edu, on 03/08/2012 at 12:15 PM, Paul Gilmartin paulgboul...@aim.com said: Better: tilde substitution in the PATH. Where I work, user homes are not in /u. And some people mount HOME via NFS from a system with YA naming standard. Is there an outstanding requirement to support UNC in z/OS Unix? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On Fri, 9 Mar 2012 08:33:11 -0500, Shmuel Metz (Seymour J.) wrote: Better: tilde substitution in the PATH. Where I work, user homes are not in /u. And some people mount HOME via NFS from a system with YA naming standard. Is there an outstanding requirement to support UNC in z/OS Unix? How would that affect the syntax or semantics of the DD PATH= parameter? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
All good points. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Wednesday, March 07, 2012 11:19 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On Wed, 7 Mar 2012 19:04:40 -0800, Charles Mills charl...@mcn.org wrote: Well, who's counting indeed, but my JCL reference says The pathname: ... - Has a length of 1 through 255 characters. ... I stand corrected; I misread earlier in the same section: Each directory or filename: Is preceded by a slash (/). The system treats any consecutive slashes as a single slash. ... Has a length of 1 through 254 characters, not including the slash. But now I've read it more carefully and submitted the RCF: Hello, MHVRCFS In: Title: z/OS V1R13.0 MVS JCL Reference Document Number: SA22-7597-15 12.48.2 Subparameter Definition pathname Is incomplete, perhaps misleading. The description appears to prohibit the following which are in fact allowed: o A pathname need not contain a filename; it may consist solely of directories, in which case it refers to a directory. o If (and only if) a pathname refers to a directory, it may end with a slash. The following may be implicit, or perhaps needs clarification: o The list of directories may be empty; the path may consist of only a filename, in which case it refers to a file in the root directory; or of only a slash, in which case it refers to the root directory itself. The following appear to be permitted, but are in fact invalid: o A slash may not appear in a directory or filename; it may be used only as a separator between directories and the filename. o The forms . and .. may not be used as filenames; these are reserved for directory names. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
This thread has very largely straightened itself out. For the record, i.e., for the sake of anyone who reads through it in the archives: 1) parameters and subparameters are of two sorts, positional and keyword 2) many historical keyword subparameters, e.g., those of the DCB= keyword parameter, have been half promoted: they continue to be usable as subparameters, but they may now also be coded as parameters 3) PARM= is a keyword parameter 4) The permissible lengths of the values of parameters vary widely [wildly?] 5) The curious restriction that positional parameters must precede keyword ones has been retained, a long, long time after its relaxation in the HLASM macro language 6) In these and other respects JCL has become a patchwork. It is no longer coherent: a knowledge of some of its facilities does not permit plausible, almost invariably confirmed conjectures about the rest of them to be made. 7) Op. cit. [in the work (already) cited] is a suitable locution for avoiding the repetitive full identification of a document. In standard scholarly usage it must be accompanied by a page number, paragraph reference, or the like; and this requirement is a particularly urgent one when the document in question contains multiple, not entirely consistent discussions of the same topic. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
PATH is not only under-specified in the JCL reference, it is also over-specified. - Is case-sensitive. Thus, /u/joe and /u/JOE and /u/Joe define three different files. Is not an aspect of the PATH= parameter, it is an aspect of the HFS. Logically they could change HFS tomorrow to be non-case-sensitive (granted, it ain't gonna happen -- I'm just talking logic here) without touching the PATH= code and the above sentence would no longer be true. Or I could write a product that mounted a remote Windows volume as an HFS volume and the above sentence would not be true. /u/Joe and /u/Fred are also different files, but that's an aspect of HFS, not of PATH=. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Wednesday, March 07, 2012 11:19 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On Wed, 7 Mar 2012 19:04:40 -0800, Charles Mills charl...@mcn.org wrote: Well, who's counting indeed, but my JCL reference says The pathname: ... - Has a length of 1 through 255 characters. ... I stand corrected; I misread earlier in the same section: Each directory or filename: Is preceded by a slash (/). The system treats any consecutive slashes as a single slash. ... Has a length of 1 through 254 characters, not including the slash. But now I've read it more carefully and submitted the RCF: Hello, MHVRCFS In: Title: z/OS V1R13.0 MVS JCL Reference Document Number: SA22-7597-15 12.48.2 Subparameter Definition pathname Is incomplete, perhaps misleading. The description appears to prohibit the following which are in fact allowed: -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On Thu, 8 Mar 2012 06:48:52 -0800, Charles Mills wrote: PATH is not only under-specified in the JCL reference, it is also over-specified. - Is case-sensitive. Thus, /u/joe and /u/JOE and /u/Joe define three different files. Is not an aspect of the PATH= parameter, it is an aspect of the HFS. Logically they could change HFS tomorrow to be non-case-sensitive (granted, it ain't gonna happen -- I'm just talking logic here) without touching the PATH= code and the above sentence would no longer be true. Or I could write a product that mounted a remote Windows volume as an HFS volume and the above sentence would not be true. /u/Joe and /u/Fred are also different files, but that's an aspect of HFS, not of PATH=. I very much agree. Add, as aspects of the HFS, not of JCL: o Multiple consecutive slashes are equivalent to a single slash, and even: o The slash serves as a directory level separator. o Any discussion that mentions the distinction between directories and filenames doesn't belong to JCL. The JCL RM should leave the specification of the UNIX filesystem(s) to another document, with citation (including page number), and mention only the limitations peculiar to JCL (and allocation) such as: o Pathnames must be absolute (start with /) o 255 character limit o restriction on permissible characters o (Others?) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On Thu, 8 Mar 2012 09:02:47 -0500, John Gilmore wrote: 2) many historical keyword subparameters, e.g., those of the DCB= keyword parameter, have been half promoted: they continue to be usable as subparameters, but they may now also be coded as parameters All DCB subparameters, or only some? And when used in connection with PATH=..., they may be used only as parameters, not as DCB subparameters. I suspect the need to enforce this restriction embodies the rationale for promotion of those subparameters. 5) The curious restriction that positional parameters must precede keyword ones has been retained, a long, long time after its relaxation in the HLASM macro language But note that despite appearance PGM=... is not a keyword parameter but a positional parameter whose allowable values are required to contain =. 6) In these and other respects JCL has become a patchwork. It is no longer coherent: a knowledge of some of its facilities does not permit plausible, almost invariably confirmed conjectures about the rest of them to be made. In this respect, it's highly consistent with the specification of HLASM. 7) Op. cit. [in the work (already) cited] is a suitable locution for avoiding the repetitive full identification of a document. In standard scholarly usage it must be accompanied by a page number, paragraph reference, or the like; and this requirement is a particularly urgent one when the document in question contains multiple, not entirely consistent discussions of the same topic. not entirely consistent could be material for an RCF. Would loc. cit. have been better? (But I was merely too lazy to verify the reference.) The online IBM manuals are infuriating in this respect: They provide a link to the publication title, but not to the page nor the chapter title, and when I follow the link I am presented with a list of every edition of publications matching the title. I hate JCL! -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On 3/8/2012 7:28 AM, Paul Gilmartin wrote: o Pathnames must be absolute (start with /) This is an inconvenience I wish could be rectified. No leading slash should default to one's home directory. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Duh! The whole point of home directories. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Edward Jaffe Sent: Thursday, March 08, 2012 7:47 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On 3/8/2012 7:28 AM, Paul Gilmartin wrote: o Pathnames must be absolute (start with /) This is an inconvenience I wish could be rectified. No leading slash should default to one's home directory. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On 8 March 2012 10:46, Edward Jaffe edja...@phoenixsoftware.com wrote: On 3/8/2012 7:28 AM, Paul Gilmartin wrote: o Pathnames must be absolute (start with /) This is an inconvenience I wish could be rectified. No leading slash should default to one's home directory. When, and on which system, would this be evaluated? Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
And, I guess, give a JCL error if the user does not have an OMVS segment, or no HOME directory specified in their OMVS segment. I agree this would be easier. But can be emulated with: PATH='/u/SYSUID/file.ext' __if__ the HOME directory is in UPPER CASE. Unfortunately, as I have UNIX set up, the HOME directory use the RACF id after it has been converted to lower-case. I pity any z/OS UNIX user whose RACF id contains a $ anywhere it in. /u/$racf/some.file will likely fail unless the environment variable racf is export'ed with a value of $racf. I guess that the /etc/profile could be set up to export the environmet variable racf set to $racf and mark it READONLY. Which only helps in a shell. And a RACF id like: a$b would be a real terror to fix in /etc/profile. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Edward Jaffe Sent: Thursday, March 08, 2012 9:47 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On 3/8/2012 7:28 AM, Paul Gilmartin wrote: o Pathnames must be absolute (start with /) This is an inconvenience I wish could be rectified. No leading slash should default to one's home directory. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Personally, I'd say on the executing system. In any case, __something__ would need to expand the simple file.ext to /path/to/home/file.ext. I guess that would be either during: JCL conversion or JCL interpretation or step execution. Now, UNIX has the concept of current working directory. I think this is generally set when the address space is dubbed, at least for a batch job which is what we're talking about since we're talking JCL (OK, or STC or TSU) and we don't have any inheritance due to fork(). When you UNIX open() a file with a relative path in it, it is relative to the current working directory. So I would consider execution time the proper time to do this. Just make sure that the current working directory for the address space is set to the HOME when it is first dubbed. Of course, if the program is using UNIX services, it could change the current working directory. That would then become the base for the pathname in the open(). Which could be ! very confusing to the ignorant user. So that could be yet another argument against using relative path names in PATH=. Reduction in confusion as to exactly which file is really being opened. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Tony Harminc Sent: Thursday, March 08, 2012 10:11 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On 8 March 2012 10:46, Edward Jaffe edja...@phoenixsoftware.com wrote: On 3/8/2012 7:28 AM, Paul Gilmartin wrote: o Pathnames must be absolute (start with /) This is an inconvenience I wish could be rectified. No leading slash should default to one's home directory. When, and on which system, would this be evaluated? Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Hey John, You saying the working directory on Z/os unix is different than the homes? Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 8, 2012, at 11:44 AM, McKown, John john.mck...@healthmarkets.com wrote: Personally, I'd say on the executing system. In any case, __something__ would need to expand the simple file.ext to /path/to/home/file.ext. I guess that would be either during: JCL conversion or JCL interpretation or step execution. Now, UNIX has the concept of current working directory. I think this is generally set when the address space is dubbed, at least for a batch job which is what we're talking about since we're talking JCL (OK, or STC or TSU) and we don't have any inheritance due to fork(). When you UNIX open() a file with a relative path in it, it is relative to the current working directory. So I would consider execution time the proper time to do this. Just make sure that the current working directory for the address space is set to the HOME when it is first dubbed. Of course, if the program is using UNIX services, it could change the current working directory. That would then become the base for the pathname in the open(). Which could b! e ! very confusing to the ignorant user. So that could be yet another argument against using relative path names in PATH=. Reduction in confusion as to exactly which file is really being opened. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Tony Harminc Sent: Thursday, March 08, 2012 10:11 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On 8 March 2012 10:46, Edward Jaffe edja...@phoenixsoftware.com wrote: On 3/8/2012 7:28 AM, Paul Gilmartin wrote: o Pathnames must be absolute (start with /) This is an inconvenience I wish could be rectified. No leading slash should default to one's home directory. When, and on which system, would this be evaluated? Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford Sent: Thursday, March 08, 2012 11:02 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field Hey John, You saying the working directory on Z/os unix is different than the homes? Sent from my iPad Scott Ford Sure current working directory is not always the HOME subdirectory. It is whatever directory was last referenced via the cd command or the C chdir() function or via the callable services: BPX1CHD (24/31 bit) or BPX4CHD (64 bit). -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On Thu, 8 Mar 2012 11:29:38 -0600, McKown, John wrote: -Original Message- [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford Sent: Thursday, March 08, 2012 11:02 AM You saying the working directory on Z/os unix is different than the homes? I really, really hope that was intended as whimsy. Sure current working directory is not always the HOME subdirectory. It is whatever directory was last referenced via the cd command or the C chdir() function or via the callable services: BPX1CHD (24/31 bit) or BPX4CHD (64 bit). Or with Rexx address SYSCALL chdir ... And this works even under TSO, and it stays changed after the EXEC or program exits. Yes, I'd like to see DYNALLOC respect CWD. But the problem remains: should the binding be performed at time of allocation, or at time of OPEN? Even now, one can DYNALLOC a path; delete the referenced file, then OPEN, which fails. IBM has taken a RCF on this WAD behavior. Better: tilde substitution in the PATH. Where I work, user homes are not in /u. And some people mount HOME via NFS from a system with YA naming standard. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
John, thanks for the clarification. Have used z/os unix some I am not the wizard you are.. Used fedora and rh some ..hopefully more later Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 8, 2012, at 12:29 PM, McKown, John john.mck...@healthmarkets.com wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford Sent: Thursday, March 08, 2012 11:02 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field Hey John, You saying the working directory on Z/os unix is different than the homes? Sent from my iPad Scott Ford Sure current working directory is not always the HOME subdirectory. It is whatever directory was last referenced via the cd command or the C chdir() function or via the callable services: BPX1CHD (24/31 bit) or BPX4CHD (64 bit). -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
In 5b3c73e7-6309-4438-b9ac-9e002f989...@yahoo.com, on 03/07/2012 at 05:30 PM, Scott Ford scott_j_f...@yahoo.com said: There is a limitation on parms of 100 bytes if memory serves me. The PARM keyword parameter of EXEC has a limit of 100; the PATH keyword parameter of DD does not. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Tips for continuing DD statement with only one parameter field
I've got several DD statements in a proc that have only a single parameter, PATH='long/path/name' Because the path is long the statement will not fit on a single card image (but the PATH parameter by itself will). So I coded //MYDDNAME DD // PATH='long/path/name' No good. It turns out the JCL Reference means what it says when it says you can break a JCL statement *after* any parameter (but not, apparently, before any parameter!). Putting an X in column 72 does not help. Putting a solo comma somewhere after DD does not help. The JCL reference does not provide any guidance that I could find. Google does not seem to know how to do this. I'm sure I could wrestle with the rules for continuing quoted parameters, but that makes an obscure, difficult to maintain mess IMHO. Do any of you more experienced JCL jockeys know a simple trick for getting around this problem? Is there some DD parameter that I should code as a no-op on the first line? Thanks all. Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
I don't know if it will work, but try SETting your path to a variable and then use that variable in the PATH= parameter: // SET MYPATH='long/path/name' //MYDDNAME DD PATH='MYPATH' C- Charles (Chuck) Hardee Senior Systems Engineer Database Administration Information Technology Services Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 724-517-2633 (Office) chuck.har...@thermofisher.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Charles Mills Sent: Wednesday, March 07, 2012 3:09 PM To: IBM-MAIN@bama.ua.edu Subject: Tips for continuing DD statement with only one parameter field I've got several DD statements in a proc that have only a single parameter, PATH='long/path/name' Because the path is long the statement will not fit on a single card image (but the PATH parameter by itself will). So I coded //MYDDNAME DD // PATH='long/path/name' No good. It turns out the JCL Reference means what it says when it says you can break a JCL statement *after* any parameter (but not, apparently, before any parameter!). Putting an X in column 72 does not help. Putting a solo comma somewhere after DD does not help. The JCL reference does not provide any guidance that I could find. Google does not seem to know how to do this. I'm sure I could wrestle with the rules for continuing quoted parameters, but that makes an obscure, difficult to maintain mess IMHO. Do any of you more experienced JCL jockeys know a simple trick for getting around this problem? Is there some DD parameter that I should code as a no-op on the first line? Thanks all. Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On 3/7/2012 2:11 PM, Charles Mills wrote: I've got several DD statements in a proc that have only a single parameter, PATH='long/path/name' Because the path is long the statement will not fit on a single card image (but the PATH parameter by itself will). So I coded //MYDDNAME DD // PATH='long/path/name' No good. It turns out the JCL Reference means what it says when it says you can break a JCL statement *after* any parameter (but not, apparently, before any parameter!). Putting an X in column 72 does not help. Putting a solo comma somewhere after DD does not help. The JCL reference does not provide any guidance that I could find. Google does not seem to know how to do this. I'm sure I could wrestle with the rules for continuing quoted parameters, but that makes an obscure, difficult to maintain mess IMHO. Do any of you more experienced JCL jockeys know a simple trick for getting around this problem? Is there some DD parameter that I should code as a no-op on the first line? Couldn't you code PATHDISP on the first line? -- Richard -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
I cheat: // SET FILE1='/usr/lpp' // SET FILE2='/tcpip' // SET FILE3='/samples' //* OTHER STUFF //MYDDNAME DD PATH='FILE1FILE2FILE3' //* I do this for long PARM= values too. Works like a chump, ahh champ. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Charles Mills Sent: Wednesday, March 07, 2012 2:09 PM To: IBM-MAIN@bama.ua.edu Subject: Tips for continuing DD statement with only one parameter field I've got several DD statements in a proc that have only a single parameter, PATH='long/path/name' Because the path is long the statement will not fit on a single card image (but the PATH parameter by itself will). So I coded //MYDDNAME DD // PATH='long/path/name' No good. It turns out the JCL Reference means what it says when it says you can break a JCL statement *after* any parameter (but not, apparently, before any parameter!). Putting an X in column 72 does not help. Putting a solo comma somewhere after DD does not help. The JCL reference does not provide any guidance that I could find. Google does not seem to know how to do this. I'm sure I could wrestle with the rules for continuing quoted parameters, but that makes an obscure, difficult to maintain mess IMHO. Do any of you more experienced JCL jockeys know a simple trick for getting around this problem? Is there some DD parameter that I should code as a no-op on the first line? Thanks all. Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Ha! //MYDDNAME DD PATHDISP=, // PATH='long/path/name' works. Kinda silly, but it works. The SET symbol is not a bad idea also as there actually is a fair amount of commonality among the three paths, so I could factor out that common part into one SET symbol. Thanks, Charles -Original Message- Do any of you more experienced JCL jockeys know a simple trick for getting around this problem? Is there some DD parameter that I should code as a no-op on the first line? Couldn't you code PATHDISP on the first line? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
JCL Reference is your friend: //S1 EXEC PGM=IEFBR14,PARM='THIS IS A LONG PARAMETER WITHIN APOST // ROPHES, CONTINUED IN COLUMN 16 OF THE NEXT RECORD' Example 4 shows continuation of a parameter field when a parameter is enclosed in apostrophes. The parameter field is continued from column 71 of the first card image to column 16 of the second. APOST - 'T' has to be on 71th column ROPHES - 'R' has to be on 16th column. Another way: variables SET V1='/root/directory' SET V2='/next/very/long/dir' SET V3='/anotherdirectory' SET V4='/is/it/enough' SET V=V1v2V3V4 ... DD PATH=V JES substitution: PATH='/root/directory/next/very/long/dir/anotherdirectory/is/it/enough' -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2012 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.410.984 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Yup. That's what I was referring to when I said I'm sure I could wrestle with the rules for continuing quoted parameters, but that makes an obscure, difficult to maintain mess IMHO. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of R.S. Sent: Wednesday, March 07, 2012 1:40 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field JCL Reference is your friend: //S1 EXEC PGM=IEFBR14,PARM='THIS IS A LONG PARAMETER WITHIN APOST // ROPHES, CONTINUED IN COLUMN 16 OF THE NEXT RECORD' Example 4 shows continuation of a parameter field when a parameter is enclosed in apostrophes. The parameter field is continued from column 71 of the first card image to column 16 of the second. APOST - 'T' has to be on 71th column ROPHES - 'R' has to be on 16th column. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
There is a limitation on parms of 100 bytes if memory serves me. Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 7, 2012, at 5:20 PM, Charles Mills charl...@mcn.org wrote: Yup. That's what I was referring to when I said I'm sure I could wrestle with the rules for continuing quoted parameters, but that makes an obscure, difficult to maintain mess IMHO. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of R.S. Sent: Wednesday, March 07, 2012 1:40 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field JCL Reference is your friend: //S1 EXEC PGM=IEFBR14,PARM='THIS IS A LONG PARAMETER WITHIN APOST // ROPHES, CONTINUED IN COLUMN 16 OF THE NEXT RECORD' Example 4 shows continuation of a parameter field when a parameter is enclosed in apostrophes. The parameter field is continued from column 71 of the first card image to column 16 of the second. APOST - 'T' has to be on 71th column ROPHES - 'R' has to be on 16th column. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Many long threads here on that one ... What's worse, parm means two different things. There is a limit of 100 characters on the operand of PARM=. But I was referring to parameters in the more general sense of, as the manual says, The parameter field consists of two types of parameters: positional parameters and keyword parameters. All positional parameters must precede all keyword parameters. Keyword parameters follow the positional parameters. Some of those parms such as PATH= can have operands with a length of 255 characters. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford Sent: Wednesday, March 07, 2012 2:30 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field There is a limitation on parms of 100 bytes if memory serves me. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On 7 March 2012 18:27, Charles Mills charl...@mcn.org wrote: Many long threads here on that one ... What's worse, parm means two different things. There is a limit of 100 characters on the operand of PARM=. But I was referring to parameters in the more general sense of, as the manual says, The parameter field consists of two types of parameters: positional parameters and keyword parameters. All positional parameters must precede all keyword parameters. Keyword parameters follow the positional parameters. Even worse, they probably should've been calling them arguments all these years... Some of those parms such as PATH= can have operands with a length of 255 characters. No, uh, argument. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
That works. In fact you can also do a partial substitution using a variable. Lloyd - Original Message From: Hardee, Chuck chuck.har...@thermofisher.com To: IBM-MAIN@bama.ua.edu Sent: Wed, March 7, 2012 3:16:05 PM Subject: Re: Tips for continuing DD statement with only one parameter field I don't know if it will work, but try SETting your path to a variable and then use that variable in the PATH= parameter: // SET MYPATH='long/path/name' //MYDDNAME DD PATH='MYPATH' C- Charles (Chuck) Hardee Senior Systems Engineer Database Administration Information Technology Services Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 724-517-2633 (Office) chuck.har...@thermofisher.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Charles Mills Sent: Wednesday, March 07, 2012 3:09 PM To: IBM-MAIN@bama.ua.edu Subject: Tips for continuing DD statement with only one parameter field I've got several DD statements in a proc that have only a single parameter, PATH='long/path/name' Because the path is long the statement will not fit on a single card image (but the PATH parameter by itself will). So I coded //MYDDNAME DD // PATH='long/path/name' No good. It turns out the JCL Reference means what it says when it says you can break a JCL statement *after* any parameter (but not, apparently, before any parameter!). Putting an X in column 72 does not help. Putting a solo comma somewhere after DD does not help. The JCL reference does not provide any guidance that I could find. Google does not seem to know how to do this. I'm sure I could wrestle with the rules for continuing quoted parameters, but that makes an obscure, difficult to maintain mess IMHO. Do any of you more experienced JCL jockeys know a simple trick for getting around this problem? Is there some DD parameter that I should code as a no-op on the first line? Thanks all. Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On Wed, 7 Mar 2012 18:54:47 -0500, Tony Harminc wrote: On 7 March 2012 18:27, Charles Mills wrote: Many long threads here on that one ... What's worse, parm means two different things. There is a limit of 100 characters on the operand of PARM=. But I was referring to parameters in the more general sense of, as the manual says, The parameter field consists of two types of parameters: positional parameters and keyword parameters. All positional parameters must precede all keyword parameters. Keyword parameters follow the positional parameters. Even worse, they probably should've been calling them arguments all these years... Some of those parms such as PATH= can have operands with a length of 255 characters. No, uh, argument. No, uh, the passage Charles quoted appears verbatim in article 3.1.1 Parameter Field of: Title: z/OS V1R13.0 MVS JCL Reference Document Number: SA22-7597-15 (or have you submitted an RCF that will appear in a future edition?) Op. cit. limits PATH to 254 characters, but who's counting? Anyway, that's closer to 255 than to 100. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Well, who's counting indeed, but my JCL reference says The pathname: - Has the form: /name1/name2/name3/.../namen - Begins with a slash. - Has a length of 1 through 255 characters. The system checks the length after substituting for any symbols and before compressing any consecutive slashes. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Wednesday, March 07, 2012 5:58 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On Wed, 7 Mar 2012 18:54:47 -0500, Tony Harminc wrote: On 7 March 2012 18:27, Charles Mills wrote: Many long threads here on that one ... What's worse, parm means two different things. There is a limit of 100 characters on the operand of PARM=. But I was referring to parameters in the more general sense of, as the manual says, The parameter field consists of two types of parameters: positional parameters and keyword parameters. All positional parameters must precede all keyword parameters. Keyword parameters follow the positional parameters. Even worse, they probably should've been calling them arguments all these years... Some of those parms such as PATH= can have operands with a length of 255 characters. No, uh, argument. No, uh, the passage Charles quoted appears verbatim in article 3.1.1 Parameter Field of: Title: z/OS V1R13.0 MVS JCL Reference Document Number: SA22-7597-15 (or have you submitted an RCF that will appear in a future edition?) Op. cit. limits PATH to 254 characters, but who's counting? Anyway, that's closer to 255 than to 100. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
Charles, That's good, 254 chars, you ave several ways to handle it ... Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 7, 2012, at 10:04 PM, Charles Mills charl...@mcn.org wrote: Well, who's counting indeed, but my JCL reference says The pathname: - Has the form: /name1/name2/name3/.../namen - Begins with a slash. - Has a length of 1 through 255 characters. The system checks the length after substituting for any symbols and before compressing any consecutive slashes. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Wednesday, March 07, 2012 5:58 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On Wed, 7 Mar 2012 18:54:47 -0500, Tony Harminc wrote: On 7 March 2012 18:27, Charles Mills wrote: Many long threads here on that one ... What's worse, parm means two different things. There is a limit of 100 characters on the operand of PARM=. But I was referring to parameters in the more general sense of, as the manual says, The parameter field consists of two types of parameters: positional parameters and keyword parameters. All positional parameters must precede all keyword parameters. Keyword parameters follow the positional parameters. Even worse, they probably should've been calling them arguments all these years... Some of those parms such as PATH= can have operands with a length of 255 characters. No, uh, argument. No, uh, the passage Charles quoted appears verbatim in article 3.1.1 Parameter Field of: Title: z/OS V1R13.0 MVS JCL Reference Document Number: SA22-7597-15 (or have you submitted an RCF that will appear in a future edition?) Op. cit. limits PATH to 254 characters, but who's counting? Anyway, that's closer to 255 than to 100. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Tips for continuing DD statement with only one parameter field
On Wed, 7 Mar 2012 19:04:40 -0800, Charles Mills charl...@mcn.org wrote: Well, who's counting indeed, but my JCL reference says The pathname: ... - Has a length of 1 through 255 characters. ... I stand corrected; I misread earlier in the same section: Each directory or filename: Is preceded by a slash (/). The system treats any consecutive slashes as a single slash. ... Has a length of 1 through 254 characters, not including the slash. But now I've read it more carefully and submitted the RCF: Hello, MHVRCFS In: Title: z/OS V1R13.0 MVS JCL Reference Document Number: SA22-7597-15 12.48.2 Subparameter Definition pathname Is incomplete, perhaps misleading. The description appears to prohibit the following which are in fact allowed: o A pathname need not contain a filename; it may consist solely of directories, in which case it refers to a directory. o If (and only if) a pathname refers to a directory, it may end with a slash. The following may be implicit, or perhaps needs clarification: o The list of directories may be empty; the path may consist of only a filename, in which case it refers to a file in the root directory; or of only a slash, in which case it refers to the root directory itself. The following appear to be permitted, but are in fact invalid: o A slash may not appear in a directory or filename; it may be used only as a separator between directories and the filename. o The forms . and .. may not be used as filenames; these are reserved for directory names. If all this is explicit in other IBM publications, it would be better to shorten 12.48.2 and supply a cross-reference to such publications. Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
