|
View previous topic :: View next topic
|
| Author |
Message |
Stefan
Active User
Joined: 12 Jan 2006
Posts: 110
Location: Germany
|
|
|
|
I want to automate most of the additional steps which developers of CICS programs have to perform to make their modules available.
I've already written a CICS program which issues "SET PROGRAM(...) PHASEIN". This program is invoked via the CICS SupportPac CA1D using the EXCI LINK interface in a batch step which follows the compile/linkedit process.
The problem is that my program does not work when the application program is new to CICS. I have to ensure that a new program is defined and installed in a group instead of being "refreshed" by PHASEIN.
I haven't found any SPI commands available to COBOL which do these things.
Any idea on how to accomplish this task? |
|
| Back to top |
|
 |
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
If you have program autoinstall specified in the SIT, you might try to just EXEC CICS LOAD the new program which would dynamically create a PPT entry. There'd be no need to then NEWCOPY as the program is unknown to CICS.
So, potentially, INQUIRE on the program and if present NEWCOPY else LOAD.
Garry. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Stefan,
CEDA Installs can be done two ways -
01) Via the CEDA transaction (you probably know this)
02) Via the CEDA/CICS Interface module "DFHEDAP"
I have two Assembler programs, one EXCI/Assembler (Client) and the other a Server (regular CICS/Assembler).
The Client program is fed the actual CEDA command via SYSIN cards in a Batch JOB and passes it to the Server program (via an EXCI-DPL), who then issues a LINK-API to "DFHEDAP" and performs the INSTALL.
The IBM Batch-Interface to CEDA "DFHCSDUP" is recommended for use other than "INSTALLS", which it can't perform.
Contact me privately if you like a copy of these programs along with the JCL.
Mr. Bill |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| I have to ensure that a new program is defined and installed in a group instead of being "refreshed" by PHASEIN. |
IIRC the refresh will fail anyway if a program has never been used,
when used for the first time CICS will use the latest object
for the test regions my suggestion is to autoinstall the programs to lessen the admministrative burden |
|
| Back to top |
|
|
Jose Mateo
Active User
Joined: 29 Oct 2010
Posts: 121
Location: Puerto Rico
|
|
|
|
Hi, Stefan!
I think problem is that the new program was define thru RDO which is not define permanently in the CICS tables. Your 'SET PROGRAM (...) PHASIN' searches in the CICS table for the program address in order to do the load. |
|
| Back to top |
|
|
Stefan
Active User
Joined: 12 Jan 2006
Posts: 110
Location: Germany
|
|
|
|
Hi guys,
many thanks for your quick responses. 
Meanwhile I've found a solution published in Xephon Update issue 165 (dated august 1999). It consists of a CICS assembler program calling DFHEDAP (the program behind CEDA), a REXX programm calling that assembler program using the same EXCI interface I've already mentioned in my original post above, and an ISPF panel to enter any valid CEDA command and show the results.
It'll be no rocket science to integrate this into my batch processing sequence.
@Bill - Thank you for offering your solution. I assume your asm module will not diverge substantially from the one I've found. |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
You need to consider a product like BatchCICS-Connect that can execute and interact with any CICS transaction from within a batch program's logic (including CEDA).
Use [URL] BBCode for External Links |
|
| Back to top |
|
|
|
|
