Well, in the PDS, there is a $$README. This is alpha code. I hadn't planned on
submitting it to the CBT until is was a bit more complete. But I was talking
over some other things with Sam Golub and he asked me to submit it "as is" even
though parts of it are very rough.
<overview>
ams - Invokes the IDCAMS batch program, redirecting SYSIN from the
UNIX "stdin" and the SYSPRINT to "stdout". The source is in ams.s.
isgquery.o - is a subroutine (object code) used by lsenq which does the
ISGQUERY macro. The source is in isgquery.s.
lsdasd - Lists the space on all on-line DASD volumes. I plan, some day,
to include the storage group name for SMS managed volumes in
the output, and to allow specification of volume series, with
"wildcarding" to subset the list. The source is in lsdasd.s.
lsenq - Lists enqueue information. You can specify a resource name, with
wildcarding. You may also specify an queue name. If a queue name
is not specified, it defaults to SYSDSN. The queue name can also
be wild carded. Also, if (and only if) the queue name is
defaulted, the resource name is assumed to be a dataset name and
is upper cased.
Syntax: lsenq [[qname] rname].
mkjcl - is a shell script, not a compiled program. It reads a "template"
file, which is specified on the command line, and modifies it by
replacing embedded UNIX-style (environment) variables with their
values. It
writes its output to "stdout" so that it may be piped to a
subsequent command, such as "submit". The variables are passed
to the command as shell environment variables, via the export
command, or on the command line itself. This is the normal way
that named variables are done in UNIX. An example of a template
jcl is supplied in the "iefbr14.jcl" file.
All files which have file name of SKELETON are just that, my SKELETON
files which I use as the basis for the actual program code. The suffix
specifies the language. ".1" for man source files. ".cat1" for
"compiled" man source files. ".a" for "library archive" files (which
contain object code for subroutines which are "statically linked").
".awk" for awk source files. ".o" for compiled object files. ".pl" for
Perl source files. ".rexx" for rexx programs. ".sh" for shell script
files. ".s" for HLASM source files.
</overview>
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
[email protected] * 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 Assembler List
> [mailto:[email protected]] On Behalf Of Kirk Wolf
> Sent: Friday, March 23, 2012 8:53 AM
> To: [email protected]
> Subject: Re: How to extract arguments passed from Unix command line?
>
> John,
>
> Is there an abstract of what's in the package?
>
> Kirk Wolf
> Dovetailed Technologies
> http://dovetail.com
>
> On Fri, Mar 23, 2012 at 7:32 AM, McKown, John
> <[email protected]
> > wrote:
>
> > I have some example HLASM code in "alpha" status available on the
> > CBTTape.org web site. Look for File 864 here:
> > http://www.cbttape.org/updates.htm
> >
> > I don't say that it's the best. But hopefully the code in
> "SKELETON.s"
> > will make fair sense. The file downloads like most on the
> CBT - you end up
> > with a XMIT of a PDS, which you must then RECEIVE to create
> the actual PDS.
> > But the actual code is in a pax archive, which is a member
> of the PDS.
> > There is JCL to unwind the pax member in the PDS into a z/OS UNIX
> > subdirectory. There is a makefile which you can use to do the actual
> > assemblies. I do all my z/OS UNIX assemblies from a z/OS
> UNIX shell prompt.
> >
> > Oh, my HLASM code is LE enabled. It is not an absolute
> necessity for UNIX
> > programs to be LE, but I sometimes use a C subroutine
> library call or two,
> > and that requires LE. So I make all my UNIX code LE
> enabled. Also, I debug
> > by forcing an S0C1 abend, and that causes the LE run time
> to create a
> > CEEDUMP for me in the UNIX subdirectory in which I am
> testing. So I do have
> > some reasons for liking LE. I know that many here despise
> LE. I'm rather
> > neutral on it.
> >
> > --
> > John McKown
> > Systems Engineer IV
> > IT
> >
> > Administrative Services Group
> >
> > HealthMarkets(r)
> >
> > 9151 Boulevard 26 * N. Richland Hills * TX 76010
> > (817) 255-3225 phone *
> > [email protected] * 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 Assembler List
> > > [mailto:[email protected]] On Behalf Of
> Scott Bennett
> > > Sent: Friday, March 23, 2012 2:00 AM
> > > To: [email protected]
> > > Subject: How to extract arguments passed from Unix command line?
> > >
> > > I am trying to find documentation or examples that show how I
> > > can utilize
> > > (I assume) register 1 to access the value of the arguments
> > > from a caller to
> > > my assembler routine executed under USS.
> > >
> > > For example, if my routine was called from USS as:
> > >
> > > $ myroutine arg1 arg2
> > >
> > > How can I get the value arg1 and arg2?
> > >
> > > Thanks!
> > >
> > >
> >
>
>
