Hello Terry,
Here's what's happened .. three days before my original post, I had
emailed IBM but heard nothing thus the post. Sent a reminder email to
IBM and got an instant response and as Friday wore on, a solution
(they're good).
It seems that what I'd learned here and did was correct. The missing bit
was as simple as making a copy of DFH420.SVTSC.PROCLIB(CICSTS42) to my
VENDOR.PROCLIB (apparently being on the pecking chain (which was in the
Dallas documentation but I knew too little to comprehend)) and
concatenating a // DD DSN=VENDOR.LOADUSER,DISP=SHR (where I stick pgms
and maps) to the DFHRPL stmt therein .. is an example of your 'pristine'
I think.
.. anyway my menu scrn appeared! Am a happy camper. Everything's simple
- if you know how.
Small downside was getting PROG755's in some of my maps that never
appeared with the same transaction in TXSeries .. will work on that
before coming back here:-).
In the meantime I would very much thank you and all who helped, am
learning more of CICS tous le temps.
Graham
------
On 24/05/2013 11:39 AM, Terry Sambrooks wrote:
Hi Graham,
Assuming that you have changed the GRPLIST in the SYSIN SIT to include your
LIST, i.er. the LIST which holds your group (GROUP1), then you should not
need to perform an INSTALL after each START=INITIAL. I use an ADCD rather
than a Dallas system but the process is the same as I mentioned in my
earlier post.
If you are able to view your CICS system via SDSF, the relevant SYSIN should
be in the JCL of that task which typically contains multiple steps, the
first two being IDCAMS executions and the third is CICS itself. The SYSIN DD
statement in this step will specify a data set name with a member name
appended and it is this member name which will contain the SIT parameters
probably starting with the APPLID. The GRPLIST parameter will be found here
also and probably only points to XYZLIST which is an IBM provided list. To
include your list simple code GRPLIST(XYZLIST,INITLIST),. (You are allowed
up to 4 lists.)
Given the data set names in your last post, and checking with the CICS42
procedure on my system I would expect the SYSIN data set to be called
DFH420.SYSIN, which contains 6 DFHSIP members. If the default from the SIP
symbolic parameter is being used then the member of interest would be
DFH$SIP$1. I would recommend copying this member and changing the last digit
so that CICS could be started with SIP=G say, to allow CICS to be started
with
/s cicsts42,SIP=G - start=initial should not be needed as it is the default
in the procedure if it standard.
I think I might have missed the DFHCSDUP ADD GROUP to LIST item as I thought
I had read that into your original post but the sequence should be:
DEFINE resources - Which creates new group if it is not already in existence
ADD Group to LIST - Which creates new list if it is not already in existence
Both of the above can be done with DFHCSDUP and if CICS is stopped and
started with the new list in GRPLIST, there is no need for INSTALL which
cannot be done via DFHCSDUP. I actually have a pair programs which exploit
the CICS EXCI interface to allow INSTALL from batch but that's another
story.
Finally if you are happy to update an IBM list then your group have been
added to XYZLIST. For preference I like to keep IBM supplied stuff pristine
thus providing a fall-back position if and when things go pear shaped.
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
