Re: Fwd: Happy 50th Birthday CICS
marktre...@gmail.com (Mark Regan) writes: > https://it.toolbox.com/blogs/trevoreddolls/happy-50th-birthday-cics-070719 As an undergraduate, within a year after taking 2hr intro to computing/fortran (they had 709 tape->tape with 1401 unit record front-end ... manually moving tapes between 709 drives and 1401 drives), I was hired fulltime to be responsible for academic and administration mainframe systems (they had 360/67 replacing 709/1401 supposedly for tss/360 which never quite came to production fruition, and so ran as 360/65 with os/360). I got to redo a lot of os/360, including sysgen. Student fortran jobs ran less than second on 709, but initially move to os/360 ran over minute (about 100 times slower). Adding HASP, cut it about in half (over 30 seconds). I then redid sysgen to carefully place datasets and members in PDS for optimal arm seek and PDS directory multi-track search ... which improved another factor of three. Last week in January 1968, three people from the science center came out to install CP67 ... which I would get to play with on weekends ... along with OS/360 work (univ. shutdown datacenter from 8am sat until 8am monday ... and I would have the place to myself, although it made any Monday morning class a little hard having gone 48hrs w/o sleep). Part of old SHARE presentation fall 1968 ... mostly CP/67 pathlength rewrites to improve OS/360 running in virtual machine (put also some amount of carefully reordered os/360 stage2 sysgen to optimize dataset arm seek and PDS directory multi-track search) http://www.garlic.com/~lynn/94.html#18 University library gets ONR grant to do online library catalog and part of the money goes for 2321 datacell. 1969 was also selected as one of the original CICS product betatest sites ... and supporting/debugging CICS was added to responsibility. One of the "bugs" was original CICS had some undocumented hard coded BDAM file options and university was using a different set of options. W/o source, it took some time to diagnose CICS startup was failing with BDAM file open (and why). lots of CICS history, gone 404 but lives on at wayback machine http://web.archive.org/web/20050409124902/http://www.yelavich.com/cicshist.htm and http://web.archive.org/web/20071124013919/http://www.yelavich.com/history/toc.htm -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
include library for @@CEETEST
Hi Would anyone know the include library for @@CEETEST I coded __ceeteest() and I guess the compiler mangled (for lack of a better term) I see CEETEST in CEE.SCEERUN alternativiliy is there some pragma option to get ride of @@ I looked in Chapter 18. z/OS XL C/C++ pragmas and didn't see any Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XL C\C++ COMPILE PRELINK and LINK
Thanks
> On Jul 7, 2019, at 5:42 PM, Don Poitras wrote:
>
> LP64 requires XPLINK. XPLINK cannot run from a PDS. I've never used the
> Debug Tool, so I can't address that. For 64-bit DLL (and main), set the
> entry point to be CELQSTRT.
>
> In article <006401d53506$febc0af0$fc3420d0$@gmail.com> you wrote:
>> HI
>
>>
>
>> I am getting the following message my source is a simple program that just
>> open a dataset. In addition since I would like to debug this from TSO I was
>> wondering if I could use __ceetest() in the code to invoke Debug tool
>
>>
>
>> Here is my source
>
>>
>
>> #include
>
>> #include
>
>> #pragma export(openadata)
>
>> #pragma csect(STATIC,"TESTDLL")
>
>> void openadata(char *filename)
>
>> {
>
>> FILE *fp = fopen("DD:TESTDD","r");
>
>> }
>
>>
>
>> Here are my compiler options
>
>>
>
>>
>
>> SET CPARM='NOOPTIMIZE,SSCOM,LIST,SOURCE,LONGNAME,RENT,DLL(NOCBA),LP
>
>>64,DEBUG(FORMAT(DWARF),LEVEL(9),SYMBOL)'
>
>>
>
>> Linker option
>
>>
>
>> LPARM='AMODE=64'
>
>>
>
>>
>
>> IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
>
>> IEW2230S 0414 MODULE HAS NO TEXT.
>
>> IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
>
>>
>
>>
>
>> I am using compile prelink and link because I would like the DLL to be in a
>> PDS
>
>>
>
>> Below Is my JCL
>
>> //*---
>
>> //* COMPILE STEP:
>
>> //*---
>
>> //COMPILE EXEC PGM=CCNDRVR,
>
>> //PARM=('/'),COND=(8,LT)
>
>> //*
>
>> //* STEPLIB DD specifies the location of the compiler and runtime
>
>> //* libraries.
>
>> //*
>
>> //STEPLIB DD DSN=CEE.SCEERUN2,DISP=SHR
>
>> // DD DSN=CEE.SCEERUN,DISP=SHR
>
>> // DD DSN=CBC.SCCNCMP,DISP=SHR
>
>> //*
>
>> //* SYSLIB DD specifies the location of the IBM-supplied C header
>
>> //* (hwthic).
>
>> //*
>
>> //SYSLIB DD DSN=SYS1.SIEAHDRV.H,DISP=SHR@01C
>
>> // DD DSN=CEE.SCEEH.H,DISP=SHR
>
>> //*
>
>> //SYSINDD DSN=IBMUSER.TEST.SOURCE(TESTDLL),DISP=SHR
>
>> //*
>
>> //* SYSLIN DD specifies the output location of the object module
>
>> //* generated by the compile step.
>
>> //*
>
>> //SYSLIN DD DSN=&,UNIT=,
>
>> // DISP=(MOD,PASS),SPACE=(TRK,(3,3)),
>
>> // DCB=(RECFM=FB,LRECL=80,BLKSIZE=)
>
>> //SYSPRINT DD SYSOUT=*
>
>> //SYSCPRT DD DSN=IBMUSER.TEST.SYSPRINT(TESTDLL),DISP=SHR
>
>> //*
>
>> //*-
>
>> //* PRE-LINKEDIT STEP:
>
>> //*-
>
>> //PLKED EXEC PGM=EDCPRLK,
>
>> //PARM='',COND=(4,LT,COMPILE)
>
>> //STEPLIB DD DSN=CEE.SCEERUN2,DISP=SHR
>
>> // DD DSN=CEE.SCEERUN,DISP=SHR
>
>> //SYSMSGS DD DSN=CEE.SCEEMSGP(),DISP=SHR
>
>> //SYSLIB DD DSN=CEE.SCEEOBJ,DISP=SHR
>
>> // DD DSN=CEE.SCEECPP,DISP=SHR
>
>> // DD DSN=CEE.SCEERUN,DISP=SHR
>
>> // DD DSN=CEE.SCEERUN2,DISP=SHR
>
>> //*
>
>> //* SYSIN DD specifies the object module generated by the compile
>
>> //*
Re: XL C\C++ COMPILE PRELINK and LINK
LP64 requires XPLINK. XPLINK cannot run from a PDS. I've never used the
Debug Tool, so I can't address that. For 64-bit DLL (and main), set the
entry point to be CELQSTRT.
In article <006401d53506$febc0af0$fc3420d0$@gmail.com> you wrote:
> HI
>
> I am getting the following message my source is a simple program that just
> open a dataset. In addition since I would like to debug this from TSO I was
> wondering if I could use __ceetest() in the code to invoke Debug tool
>
> Here is my source
>
> #include
> #include
> #pragma export(openadata)
> #pragma csect(STATIC,"TESTDLL")
> void openadata(char *filename)
> {
> FILE *fp = fopen("DD:TESTDD","r");
> }
>
> Here are my compiler options
>
>
> SET CPARM='NOOPTIMIZE,SSCOM,LIST,SOURCE,LONGNAME,RENT,DLL(NOCBA),LP
> 64,DEBUG(FORMAT(DWARF),LEVEL(9),SYMBOL)'
>
> Linker option
>
> LPARM='AMODE=64'
>
>
> IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
> IEW2230S 0414 MODULE HAS NO TEXT.
> IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
>
>
> I am using compile prelink and link because I would like the DLL to be in a
> PDS
>
> Below Is my JCL
> //*---
> //* COMPILE STEP:
> //*---
> //COMPILE EXEC PGM=CCNDRVR,
> //PARM=('/'),COND=(8,LT)
> //*
> //* STEPLIB DD specifies the location of the compiler and runtime
> //* libraries.
> //*
> //STEPLIB DD DSN=CEE.SCEERUN2,DISP=SHR
> // DD DSN=CEE.SCEERUN,DISP=SHR
> // DD DSN=CBC.SCCNCMP,DISP=SHR
> //*
> //* SYSLIB DD specifies the location of the IBM-supplied C header
> //* (hwthic).
> //*
> //SYSLIB DD DSN=SYS1.SIEAHDRV.H,DISP=SHR@01C
> // DD DSN=CEE.SCEEH.H,DISP=SHR
> //*
> //SYSINDD DSN=IBMUSER.TEST.SOURCE(TESTDLL),DISP=SHR
> //*
> //* SYSLIN DD specifies the output location of the object module
> //* generated by the compile step.
> //*
> //SYSLIN DD DSN=&,UNIT=,
> // DISP=(MOD,PASS),SPACE=(TRK,(3,3)),
> // DCB=(RECFM=FB,LRECL=80,BLKSIZE=)
> //SYSPRINT DD SYSOUT=*
> //SYSCPRT DD DSN=IBMUSER.TEST.SYSPRINT(TESTDLL),DISP=SHR
> //*
> //*-
> //* PRE-LINKEDIT STEP:
> //*-
> //PLKED EXEC PGM=EDCPRLK,
> //PARM='',COND=(4,LT,COMPILE)
> //STEPLIB DD DSN=CEE.SCEERUN2,DISP=SHR
> // DD DSN=CEE.SCEERUN,DISP=SHR
> //SYSMSGS DD DSN=CEE.SCEEMSGP(),DISP=SHR
> //SYSLIB DD DSN=CEE.SCEEOBJ,DISP=SHR
> // DD DSN=CEE.SCEECPP,DISP=SHR
> // DD DSN=CEE.SCEERUN,DISP=SHR
> // DD DSN=CEE.SCEERUN2,DISP=SHR
> //*
> //* SYSIN DD specifies the object module generated by the compile
> //* step as input to the prelinker.
> //*
> //SYSINDD DSN=*.COMPILE.SYSLIN,DISP=(MOD,DELETE)
> // DD
XL C\C++ COMPILE PRELINK and LINK
HI
I am getting the following message my source is a simple program that just
open a dataset. In addition since I would like to debug this from TSO I was
wondering if I could use __ceetest() in the code to invoke Debug tool
Here is my source
#include
#include
#pragma export(openadata)
#pragma csect(STATIC,"TESTDLL")
void openadata(char *filename)
{
FILE *fp = fopen("DD:TESTDD","r");
}
Here are my compiler options
SET CPARM='NOOPTIMIZE,SSCOM,LIST,SOURCE,LONGNAME,RENT,DLL(NOCBA),LP
64,DEBUG(FORMAT(DWARF),LEVEL(9),SYMBOL)'
Linker option
LPARM='AMODE=64'
IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
IEW2230S 0414 MODULE HAS NO TEXT.
IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
I am using compile prelink and link because I would like the DLL to be in a
PDS
Below Is my JCL
//*---
//* COMPILE STEP:
//*---
//COMPILE EXEC PGM=CCNDRVR,
//PARM=('/'),COND=(8,LT)
//*
//* STEPLIB DD specifies the location of the compiler and runtime
//* libraries.
//*
//STEPLIB DD DSN=CEE.SCEERUN2,DISP=SHR
// DD DSN=CEE.SCEERUN,DISP=SHR
// DD DSN=CBC.SCCNCMP,DISP=SHR
//*
//* SYSLIB DD specifies the location of the IBM-supplied C header
//* (hwthic).
//*
//SYSLIB DD DSN=SYS1.SIEAHDRV.H,DISP=SHR@01C
// DD DSN=CEE.SCEEH.H,DISP=SHR
//*
//SYSINDD DSN=IBMUSER.TEST.SOURCE(TESTDLL),DISP=SHR
//*
//* SYSLIN DD specifies the output location of the object module
//* generated by the compile step.
//*
//SYSLIN DD DSN=&,UNIT=,
// DISP=(MOD,PASS),SPACE=(TRK,(3,3)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=)
//SYSPRINT DD SYSOUT=*
//SYSCPRT DD DSN=IBMUSER.TEST.SYSPRINT(TESTDLL),DISP=SHR
//*
//*-
//* PRE-LINKEDIT STEP:
//*-
//PLKED EXEC PGM=EDCPRLK,
//PARM='',COND=(4,LT,COMPILE)
//STEPLIB DD DSN=CEE.SCEERUN2,DISP=SHR
// DD DSN=CEE.SCEERUN,DISP=SHR
//SYSMSGS DD DSN=CEE.SCEEMSGP(),DISP=SHR
//SYSLIB DD DSN=CEE.SCEEOBJ,DISP=SHR
// DD DSN=CEE.SCEECPP,DISP=SHR
// DD DSN=CEE.SCEERUN,DISP=SHR
// DD DSN=CEE.SCEERUN2,DISP=SHR
//*
//* SYSIN DD specifies the object module generated by the compile
//* step as input to the prelinker.
//*
//SYSINDD DSN=*.COMPILE.SYSLIN,DISP=(MOD,DELETE)
// DD DSN=CBC.SCLBSID(IOSTREAM),DISP=SHR
//*
//* SYSMOD DD specifies the output dataset to contain the prelinked
//* object module generated by the prelinker.
//*
//SYSMOD DD DSN=&,UNIT=,DISP=(NEW,PASS),
//
Fwd: Happy 50th Birthday CICS
https://it.toolbox.com/blogs/trevoreddolls/happy-50th-birthday-cics-070719 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Job abend with S722
On Fri, 5 Jul 2019 19:06:04 +0530, raji ece wrote: >One of our job is abending with RC S722 and the error show the maximum >outlimit execeed. We have coded lines=99(Maximum limit) and run but >getting same error. Current zos level is 1.13. any idea? > Did the job ABEND before it has been given control? If a job has a lot of steps, each with a lot of DD statements that are using variable symbols, causing an additional "IEFC653I SUBSTITUTION JCL..." line to be produced for every statement using variable symbol(s), than output limit could be exceeded before the job gets control, since you can't specify OUTLIM for the JESJCL dataset. Installation EXIT9 should tolerate such a condition. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
