On Oct 26, 2016, at 9:17 AM, Charles Mills <[email protected]> wrote: > > Sounds like this is slightly bleeding edge. I think I will try to sync my > "code management" processes (C versus HLASM) a little more closely together > but continue to keep HLASM source and object in a PDSE.
I’ll just throw out what I do. I keep the source in HFS (but not object; that’s still in a PDSE) and use OCOPY to put it in a temporary dataset for the assembler. Something like this: //EXTRSRCE EXEC PGM=IKJEFT01,DYNAMNBR=300 //SYSTSPRT DD SYSOUT=Q //SYSPRINT DD SYSOUT=Q //SOURCE DD PATH=‘/path-to-source/mypgm.s' //SYSAIN DD DSN=&&SRCE,DISP=(,PASS),DATACLAS=SRC //SYSTSIN DD * OCOPY INDD(SOURCE) OUTDD(SYSAIN) /* //ASMLINK EXEC HLASMCL //C.SYSIN DD DISP=OLD,DSN=&&SRCE … -- Pew, Curtis G [email protected] ITS Systems/Core/Administrative Services ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
