On Fri, Jan 05, 2024 at 12:17:26PM -0800, John James wrote:
So I ran the DL/I application in MVT/HASP, on the basis that it ought to
work, and would provide some sort of baseline. The PSBGEN, COBOL compile,
and link, all went fine. But the DBDGEN gave me several MNOTE-style
errors, which I thought I had fixed, but maybe not. The DLIBATCH execution
failed 0C5 as soon as the COBOL program got control. I suspect that the
parameter list passed by DFSIRC00 was invalid, but I still have some work
to to on the dump.
Did you link the DL/I SVC into the nucleus? Rummaging around I think this
is the job I used to link the HASP and DL/I SVCs into a nucleus on the
MVT/HASP system I tried it on:
//P05LSVC JOB 1,'P05LSVC HASP 4',MSGLEVEL=(1,1),CLASS=A,MSGCLASS=A
//****
//* ***
//* Job: P05LSVC ***
//* Product: HASP V4 for MVT. ***
//* Purpose: Link HASP and DL/I SVCs into the nucleus. ***
//* Update: 2003/01/26 ***
//* ***
//****
//*
//LINKSVC EXEC PGM=IEWL,REGION=192K,
// PARM='NCAL,DC,SIZE=(128K,6K),SCTR,LET,LIST,XREF'
//HASPOBJ DD DISP=SHR,DSN=SYS1.HASPOBJ
//DLIRESLB DD DISP=SHR,DSN=DLI.RESLIB
//SVCLIB DD DISP=SHR,DSN=SYS1.SVCLIB
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(10,5))
//SYSLMOD DD DISP=SHR,DSN=SYS1.NUCLEUS
//SYSPRINT DD SYSOUT=A
//SYSLIN DD *
INSERT IEAANIP0
INSERT IEAQFX00
INCLUDE HASPOBJ(HASPSVC)
INCLUDE DLIRESLB(IGG019Z9)
INCLUDE DLIRESLB(IGC230)
INCLUDE SVCLIB(IGC0024H)
INCLUDE SYSLMOD(IEANUC01)
NAME IEANUC01(R)
/*
//
/*EOF
I think that used an alternate nucleus for testing and there were some steps
I can't remember that had to be performed before/during the IPL in Hercules
to select the alternate nucleus. There might also be some other steps
needed with the SVC that I'm forgetting. Does it need to be in an SVC table
somewhere, perhaps in the OS SysGen?
--
Kevin
Bruceville, TX
What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
