So lemme show ?ya ...
// ASSGN SYS007,SYSPCH? <---- job life assignment of SYS007 to the POWER punch
// ASSGN SYS000,SYSLNK <---- job life assignment of SYS000 to SYSLNK
...
// DLBL IJSYSPH,'FUNC2.OBJ',0,SD ?<------ Assign SYSPCH?to a disk file
// EXTENT SYSPCH,,,,12000,500 SPACE-OBJ
ASSGN SYSPCH,SYS000 <----- Perm assignment of SYSPCH?to SYS000 ...
So you have it set up as:
SYSPCH?> SYS000 > SYSLNK
... The right way to do this is:
// DLBL IJSYSPH,'FUNC2.OBJ',0,SD ?<------ Assign SYSPCH?to a disk file
// EXTENT SYSPCH,,,,12000,500 SPACE-OBJ
Joe
On Sat, Sep? 7, 2024 at 08:44 PM, Joe Monk wrote:
> So setup all your logicals at the beginning of the job, and only change
> when necessary. All logicals should ALWAYS be assigned with // ASSGN, NEVER
> with ASSGN in a JOB.
I got an error when I tried adding // to my ASSGNs, but I
have since managed to figure out how to dump object
code, one at a time, via separate JCL below.
So now hopefully the pdld author will be able to support
VS(E) as a target. To be combined with as370 as the
assembler, and gcc370 as the C compiler. So that executables
suitable for running on DOS/VS as well as z/VSE and VSEn
can be built on Windows.
BFN. Paul.
* $$ JOB JNM=VSEJOB
* $$ LST LST=SYSLST,CLASS=A
// JOB VSEJOB
*
*
*
* Standard assignments for C programs
*
// ASSGN SYS000,SYSLNK
// ASSGN SYS005,SYSLST
// ASSGN SYS007,SYSPCH
// OPTION DUMP
*
*
*
*
*
*
* Now assemble the main routine
*
// DLBL IJSYSPH,'FUNC2.OBJ',0,SD
// EXTENT SYSPCH,,,,12000,500 SPACE-OBJ
ASSGN SYSPCH,SYS000
// OPTION DECK,NOEDECK
// EXEC ASSEMBLY
undivert(func2.asm)dnl
/*
CLOSE SYSPCH,PUNCH
*
*
*
*
// DLBL SDI1,'FUNC2.OBJ'
// TLBL MTO1,'HERC01.MFTOPC',0
// ASSGN SYS011,TAPE,VOL=MFTOPC
// EXEC VSEMANIP,SIZE=AUTO,PARM='dd:sdi1 dd:mto1'
*
*
*
/&
* $$ EOJ
|
