Hi Terry,
Thanks, am getting a bit knotted with all the incoming info helping me,
if I may ..
------
I use batch DFHCSDUP just for DEFINE'ing all my pgms, maps, files and
transid's (avg 20 each time) because is part of an automated process
(RDO is a non-starter). The entries seem to 'stick' from bounce to
bounce .. so am guessing that DFHCSDUP is OK in this context but not for
INSTALLing groups/lists what have you. I'd like to believe this because
DFHCSDUP is fundamental to my little system e.g:
//DFHCSDUP EXEC PGM=DFHCSDUP,REGION=1M,
// PARM='CSD(READWRITE),PAGESIZE(60),NOCOMPAT'
//STEPLIB DD DSN=DFH420.CICS.SDFHLOAD,DISP=SHR
//DFHCSD DD DSN=DFH420.DFHCSD,DISP=SHR
//OUTDD DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE PROGRAM(QKVSP01) GROUP(GROUP1)
DEFINE PROGRAM(QKVSP01) GROUP(GROUP1)
TRANSID(QKVA)
LANGUAGE(COBOL)
DESCRIPTION(Main_menu_pgm)
.. plus several more DEFINE's
------
About warm etc starts: being a Dallas 'guest' I am skillwise limited to
do what they say i.e..
/s cicsts42,start=initial
/f cicsts42,cemt p shut imm
.. that's my limit.
------
.. bell just rang, email from Patrick .. will now do a search for
APPLID=, I found his third sentence DEVASTATING for me, sounds like I'd
have to INSTALL my GROUP1 and INITLIST after each start=initial ..
sounds like 'not the way to go'.
------
Where should I look for 'the SYSIN DD statement in the CICS step of the
start-up JCL' .. think am asking where is the SIT table/file? Search
path I'm using is:
//NEWDD DD DSN=DFH420.SVSC.CPSM.CUSTOM.INSTALL,DISP=SHR
// DD DSN=DFH420.SVSC.CUSTOM.INSTALL,DISP=SHR
// DD DSN=DFH420.SVSC.DOCLIB,DISP=SHR
// DD DSN=DFH420.SVSC.INSTALL,DISP=SHR
// DD DSN=DFH420.SVSC.MIS.SERVICE,DISP=SHR
// DD DSN=DFH420.SVSC.PGMDIR,DISP=SHR
// DD DSN=DFH420.SVSC.README,DISP=SHR
// DD DSN=DFH420.SVSC.RIMLIB,DISP=SHR
// DD DSN=DFH420.SVSC.SAMPLES,DISP=SHR
.. is right?
------
.. the search for APPLID= and SYSIN did point to what might be
significant being ..
BROWSE DFH420.SVSC.CUSTOM.INSTALL(CEECCSD) - 01.0 Line 0
Command ===>
******************************** Top of Data **************
/DFHCSDX JOB (FB3),IBMUSER,REGION=4M,
/ CLASS=A,MSGCLASS=X,COND=(0,NE),NOTIFY=&SYSUID
/* ADD LE SUPPORT FOR CICS TS
/CSDUP EXEC PGM=DFHCSDUP,REGION=1M
/STEPLIB DD DSN=DFH420.CICS.SDFHLOAD,DISP=SHR
/DFHCSD DD DSN=DFH420.DFHCSD,DISP=SHR
/SYSPRINT DD SYSOUT=*
/SYSDUMP DD SYSOUT=*
/SYSIN DD DSN=CEE.SCEESAMP(CEECCSD),DISP=SHR
*
/CSDADD EXEC PGM=DFHCSDUP,REGION=1M
/STEPLIB DD DSN=DFH420.CICS.SDFHLOAD,DISP=SHR
/DFHCSD DD DSN=DFH420.DFHCSD,DISP=SHR
/SYSPRINT DD SYSOUT=*
/SYSDUMP DD SYSOUT=*
/SYSIN DD *
ADD GROUP(CEE) LIST(XYZLIST)
*
******************************* Bottom of Data ************
.. am I searching in the right place? am I getting closer? is this where
I might add in:
ADD GROUP(GROUP1) LIST(XYZLIST)
and did I ever need to create an INITLIST which is what I did?
------
I thank all for your patience, rest assured you won't hear from me after
I see my QKVA transid bring up my menu screen!!! .. until next time:-)
Tia
Graham
.. other kind posters .. am thinking .. help is so welcome
------
On 24/05/2013 3:27 AM, Terry Sambrooks wrote:
HI Graham,
Both Lizette and Wayne have correctly indicated that doing a CEDA INSTALL as
prior to issuing that command the transaction definition is defined within
the CSD but not available to CICS for use.
Additionally it may be worth knowing that INSTALL is not possible via
DFHCSDUP.
If CICS is started with a WARM or EMERGENCY start the CSD is not used to
refresh the resource definitions within CICS, it uses the CICS Global
Catalogue instead. If an INITIAL or COLD start is performed it will use the
CSD. Doing the INSTALL via CEDA is fine for WARM/EMERGENCY situations but to
cater for INITIAL/COLD if a new LIST has been created it is worth checking
the GRPLIST parameter in the SIT to ensure that the list is defined to CICS
start-up.
The SIT can be located by checking the member name in the data set defined
via .
Kind Regards - Terry
Director
KMS-IT Limited
228 Abbeydale Road South
Dore
Sheffield
S17 3LA
UK
Reg : 3767263
Outgoing e-mails have been scanned, but it is the recipients responsibility
to ensure their anti-virus software is up to date.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
