On Wed, 5 Feb 2025 15:00:42 -0500, Gord Tomlin wrote:
>Why not use the z/OS UNIX "as" command?
>
>It's described in the z/OS UNIX System Services Command Reference.
>
That's
<https://www.ibm.com/docs/en/zos/3.1.0?topic=descriptions-as-use-hlasm-assembler-produce-object-files>
<Gasp!>
... or write a Rexx wrapper to perform allocations with BPXWDYN()
alloc and concat, then address LINKMVS ASMA90;
Does TSO make the chore easier or harder?
>> On Wed, 5 Feb 2025 16:01:11 +0000 David Frenzel wrote:
>> :>
>> :>I am trying to execute the assembler ASMA90 with tsocmd from a shell
>> script in USS. My shell script is simple:
>> :>#!/bin/sh
>> :>
>> :>export sysin="alloc dsname('IBMUSER.BMSPDSE(BMS)') shr reuse"
>> :>export TSOALLOC=sysin
>> :>
>> :>export syslin="alloc dsname('IBMUSER.PROG.OBJ') shr reuse"
>> :>export TSOALLOC=syslin:$TSOALLOC
>> :>
>> :>export sysprint="alloc dsname('IBMUSER.BMS.SYSPRINT') shr reuse"
>> :>export TSOALLOC=sysprint:$TSOALLOC
>> :>
>> :>export syspunch="alloc dsname('IBMUSER.PROG.OBJ') shr reuse"
>> :>export TSOALLOC=syspunch:$TSOALLOC
>> :>
>> :>export sysadata="alloc dsname('IBMUSER.PROG.ADATA') shr reuse"
>> :>export TSOALLOC=sysadata:$TSOALLOC
>> :>
>> :>export sysut1="alloc lrecl(80) recfm(f,b) new"
>> :>export TSOALLOC=sysut1:$TSOALLOC
>> :>
>> :>tsocmd -d "ASMA90"
>> :>
>> :>The SYSIN data set is an FB 80 PDSE which contains a member includes a BMS
>> map. I am aware that I am missing more DDs and assembler parameters to
>> assemble a BMS map.
>> :>I am stuck earlier, ASMA90 puts this on the SYSPRINT:
>> :>** ASMA413C Unable to open INPUT file
>> :>
>> :>
>> :>HIGH LEVEL ASSEMBLER - INTERRUPT AND DIAGNOSTIC DUMP
>> :>** ASMA935U One or more required files not available
>> :>
>> :>I can only assume SYSIN is meant with “INPUT file”. When I execute a JCL
>> that allocates the same data set the assembler runs fine.
>> :>I can see some weird messages on the SYSLOG whenever I execute the script:
>> :>N 0020000 VS01 25036 11:55:08.15 STC00095 00000090 IEC130I BMUSER
>> DD STATEMENT MISSING
>> :>N 0020000 VS01 25036 11:55:08.15 STC00095 00000090 IEC130I UENU I
>> DD STATEMENT MISSING
>> :>
>> :>Any help is appreciated on a) what is causing the issue and/or b) why this
>> behaves so differently compared to a JCL.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
