COBOL/VSE compile JCL example request
Allan Peterson
My mind has hit a brick wall on the conversion of COBOL/VS to COBOL/VSE and
I need help.
I require examples of JCL to compile:
1. COBOL/VSE, that includes EXEC DLI and EXEC CICS stmts
2. COBOL/VSE, that include CALL 'CBLTDL" and EXEC CICS stmts
3. COBOL/VSE batch that includes CALL "CBLTDLI' stmts
4. COBOL/VSE batch that includes EXEC DLI stmts.
At this point we are not using any LE callable functions.
Do I need LE/VSE in my libdef's for the compiles and execution?
Where can I find the examples in the manuals as COBOL/VSE indicates go look
at CICS manuals but CICS does not refer to COBOL/VSE only COBOLII.
Thanks in advance and hope that those that attended WAVV now have their
livers back under control.
Stu...@de1.ibm.com
In article <1997111303...@out2.ibm.net>,
Yes you should put the LE lib in front of the libdef chain.
Now i just append a few hints for conversion and set up. pls check
if you have the Apars mentioned.
Good luck
Roland Stumpf
DL/I-APAR PN67649 provides full 31-bit support for HLL DL/I applications
..
HLL-Compilers, which can be used to create 31-bit DL/I applications are:
o PL/I for VSE/ESA
o COBOL for VSE/ESA
o COBOL II
o High Level Assembler
Both DL/I online and batch/MPS applications written in any of the
languages listed above can execute above the 16 MB line provided they
have the required AMODE/RMODE attributes. This is possible both for
applications implemented in the DL/I CALL and DL/I HLPI interface.
Execution of DL/I applications above the 16 MB line also includes that
the DL/I parameters can reside above the 16 MB line.
CICS/VSE online applications must be implemented with the CICS command
level interface to exploit 31-bit addressing.
CICS/VSE macro-level applications and user-created DL/I exit routines
(such as randomizing and compression routines) can not run in 31-bit
mode .
DL/I - Online:
For DL/I online applications written in PL/I for VSE/ESA the formerly
required inclusion of object module DFHPL1I must be replaced through the
inclusion of DFHELII, and the inclusion of object module PLISHRE must be
dropped. Also all programs should be compiled with option SYSTEM(CICS).
For DL/I online applications written in COBOL for VSE/ESA the job
control requirements are the same as for DL/I online applications
written in COBOL II. For all existing compilers the job control
requirements remain unchanged as described in the according DL/I
documentation. This includes the COBOL II compiler and the High Level
Assembler.
PL/I for VSE/ESA online example:
The following example illustrates the job control statements needed to
compile and link a DL/I online application written in PL/I for VSE/ESA.
For any additional non-DL/I related compiler options or definitions
please refer to the according PL/I for VSE/ESA documentation.
PL/I Online with HLPI or CALL interface
// JOB PL2SAMPL
// DLBL IJSYSPH,'PL/I TRANSLATION',yy/ddd
// EXTENT SYSPCH,extent information
ASSGN SYSPCH,DISK,VOL=volid,SHR
// LIBDEF *,SEARCH=search-libraries
// LIBDEF PHASE,CATALOG=catalog-library
// EXEC DFHEPP1$,SIZE=...
*PROCESS SYSTEM(CICS),XOPTS(CICS,DLI)
.
.
SOURCE DECK
.
.
/*
CLOSE SYSPCH,punch
// DLBL IJSYSIN,'PL/I TRANSLATION',yy/ddd
// EXTENT SYSIPT
ASSGN SYSIPT,DISK,VOL=volid,SHR
// OPTION NODECK,CATAL
PHASE PL2SAMPL,*
INCLUDE DFHELII
// EXEC IEL1AA,SIZE=...
// EXEC LNKEDT
/&
// JOB RESET
CLOSE SYSIPT,reader
/&
NOTE:
If the DL/I CALL interface is used the DLI parameter in the *PROCESS
XOPTS statement should be omitted.
DL/I - Batch:
For batch and MPS batch applications written either in COBOL for
VSE/ESA or COBOL II the inclusion of object module DLZBPJRA must be
dropped. Therefore the JCL definition for the former entry point
CBLCALLA must be replaced by the new entry point DLITCBL.
For batch and MPS batch applications written in PL/I for VSE/ESA the
inclusion of IBMBPJRA must be replaced through the inclusion of
IBMRPJRA. Also all programs should be compiled with option SYSTEM(DLI).
For all DL/I batch programs not written in COBOL for VSE/ESA, COBOL II
or PL/I for VSE/ESA the JCL requirements remain unchanged as described
in the existing DL/I documentation.
COBOL batch examples:
The following examples illustrate the job control statements needed to
compile and link a batch or batch MPS application written either in
COBOL for VSE/ESA or COBOL II language. IGYCRCTL is the name for both
compilers. If both compilers are installed the LIBDEF SEARCH chain
determines, which compiler will actually be used.
COBOL Batch and MPS batch with HLPI interface
// JOB COBSAMPL
// DLBL IJSYSPH,'COBOL TRANSLATION',yy/ddd
// EXTENT SYSPCH,extent information
ASSGN SYSPCH,DISK,VOL=volid,SHR
// LIBDEF *,SEARCH=search-libraries
// LIBDEF PHASE,CATALOG=catalog-library
// EXEC DFHECP1$,SIZE=...
CBL XOPTS(DLI,COBOL2),RES,RENT,DATA(31)
.
.
SOURCE DECK
.
.
/*
CLOSE SYSPCH,punch
// DLBL IJSYSIN,'COBOL TRANSLATION',yy/ddd
// EXTENT SYSIPT
ASSGN SYSIPT,DISK,VOL=volid,SHR
// OPTION NODECK,CATAL
PHASE COBSAMPL,*
INCLUDE DLZLICBL
// EXEC IGYCRCTL,SIZE=...
ENTRY DLITCBL
// EXEC LNKEDT
/&
// JOB RESET
CLOSE SYSIPT,reader
/&
COBOL Batch and MPS batch with CALL interface
// JOB COBSAMPL
// LIBDEF *,SEARCH=search-libraries
// LIBDEF PHASE,CATALOG=catalog-library
// OPTION NODECK,CATAL
PHASE COBSAMPL,*
// EXEC IGYCRCTL,SIZE=...
CBL LIB,RES,RENT,DATA(31)
.
.
SOURCE DECK
.
.
/*
ENTRY DLITCBL
// EXEC LNKEDT
/&
PL/I for VSE/ESA batch examples:
The following examples illustrate the job control statements needed to
compile and link a batch or batch MPS application written in PL/I for
VSE/ESA.
PL/I for VSE/ESA Batch and MPS batch with HLPI interface
// JOB PL2SAMPL
// DLBL IJSYSPH,'PL/I TRANSLATION',yy/ddd
// EXTENT SYSPCH,extent information
ASSGN SYSPCH,DISK,VOL=volid,SHR
// LIBDEF *,SEARCH=search-libraries
// LIBDEF PHASE,CATALOG=catalog-library
// EXEC DFHEPP1$,SIZE=...
*PROCESS SYSTEM(DLI),XOPTS(DLI)
.
.
SOURCE DECK
.
.
/*
CLOSE SYSPCH,punch
// DLBL IJSYSIN,'PL/I TRANSLATION',yy/ddd
// EXTENT SYSIPT
ASSGN SYSIPT,DISK,VOL=volid,SHR
// OPTION NODECK,CATAL
PHASE PL2SAMPL,*
// EXEC IEL1AA,SIZE=...
INCLUDE DLZLIPLI
INCLUDE IBMRPJRA
ENTRY DLZLIPLI
// EXEC LNKEDT
/&
// JOB RESET
CLOSE SYSIPT,reader
/&
PL/I for VSE/ESA Batch and MPS batch with CALL interface
// JOB PL2SAMPL
// LIBDEF *,SEARCH=search-libraries
// LIBDEF PHASE,CATALOG=catalog-library
// OPTION NODECK,CATAL
PHASE PL2SAMPL,*
// EXEC IEL1AA,SIZE=...
*PROCESS SYSTEM(DLI)
.
.
SOURCE DECK
.
.
/*
INCLUDE IBMRPJRA
ENTRY PLICALLB
// EXEC LNKEDT
/&
Please note that the former PL/I ISA storage is now controlled by LE for
VSE/ESA and LE for VSE/ESA uses GETVIS for storage allocation. This can
lead to an increased demand for GETVIS storage of your applications.
Additional Support for the LE/VSE Environment:
Following LE for VSE/ESA functions are additionally supported:
1. LE for VSE/ESA TRAP runtime option
PN67649 allows that DL/I batch applications implemented in one of the
LE for VSE/ESA languages can run with the LE for VSE/ESA TRAP option set
on. While TRAP(ON) is set any abnormal termination condition caused by
the application will first be treated by the LE for VSE/ESA error
routines. If DL/I is to receive control again after LE error handling
has taken place (e.g. to write back pending DL/I data buffers to
properly close the DL/I databases and/or log files)
ABTERMENC(ABEND)
or any equivalent runtime option must have been specified. Only this
guarantees proper DL/I termination when TRAP(ON) has been set.
When running with TRAP(ON) DL/I STXIT linkage is overlaid by LE for
VSE/ESA STXITs. In consequence any DL/I dumps issued by one of the DL/I
exits after message DLZ001I will not reflect the original storage
contents as at the time when the error occurred. These DL/I dumps can be
suppressed by the appropriate UPSI byte setting as described in the DL/I
manual "Resource Definition and Utilities" (SH24-5021-02).
For information on the LE for VSE/ESA TRAP option please refer to the
according LE for VSE/ESA documentation. If original DL/I STXIT linkage
and exit processing is wanted, the application should be run with
TRAP(OFF). Information on DL/I STXIT linkage can be obtained in the DL/I
manuals "Resource Definition and Utilities" referenced above and "Guide
for new Users" (SH24-5001-4).
2. LE for VSE/ESA CEETDLI interface:
LE for VSE/ESA provides a callable service, CEETDLI, that you can use
to issue DL/I calls. CEETDLI performs essentially the same functions, as
the existing language-specific interfaces (ASMTDLI, CBLTDLI, PLITDLI),
but is language independent. Only LE for VSE/ESA conforming application
code can call CEETDLI. Calls to CEETDLI are coded in the same way as
calls to the language-specific interfaces. A description of the CEETDLI
syntax can be found in the "LE for VSE/ESA Programming Guide".
The existing language-specific interfaces will continue to function in
their current capacity both in existing programs and programs newly
compiled and linked under the new LE for VSE/ESA environment.
Delivery:
PN67649 is contained in DL/I 1.10 Refreshs delived with VSE/ESA 1.4,
VSE/ESA 2.1 and their follow on releases. When PN67649 has been
installed it is required to
o generate a new DL/I nucleus (ACTGEN)
o specify PATH sensitivity for all segments for which path updates
(insert, replace) are done via 31-bit applications. This includes a new
Assembly and ACBGEN run for all affected PCBs.
o re-compile/link all user-written programs (for example, randomizing
routines) which reference any of the following DL/I control blocks:
- DLZPST
- DLZSDIB
- DLZSSAX
- DLZSSAP
Additionally all existing COBOL II batch applications
1. using the DL/I HLPI interface úúúand
2. having the attributes AMODE=31 and RMODE=ANY úúú and
3. which have been compiled before installation of PN67649
must be re-compiled and re-linked.
Any other existing DL/I applications not matching above combination of
criteria will run unchanged as before.
-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet