how to add a new group and a new loadlib to TS 1.3 ?

[HUJ]

hi,all
i just try to add a new group and a new loadlib to TS 1.3 the detail step is:
1)using CEDA define and install a new group. This group is very simple. It contain a mapset and four program and a transaction.
2)add the loadlib name where program resident in to DFHRPL
3)restart cics region again
4)logon to cics,using CESN
5)enter test transaction id
but cics always tell " CICSAC1 TRASACTION ACCT CANNOT RUN
BEACAUSE PROGRAM ACCT01 IS NOT AVAILABLE"

 

[gregsimpson]

HUJ,

have you checked the load modules are able to be picked up, say using CEMT.

Cheers
Greg

 

[HUJ]

YES, i use CEMT I PROG(acct01) to check the load module.
but it's length is always 0. it's likely cics dont't find that program. whether i need add some new cics control table besides using RDO and modify CICS startup job stream's DFHRPL. but i really don't know how to
resolve this problem. thanks for your replay.

 

[TonyJollans]

Hi HUJ,

It's a few years since I've worked on CICS so this may be inaccurate, but I have a hazy memory of there being issues with DFHRPL libraries with differing blocksizes - can't remember exactly what but it might be worth checking out to see if anything seems obvious.

Also, is it just the program that's unavailable? What about the mapsets - can you use them in CECI for example?

Enjoy,
Tony

------------------------------------------------------------------------------------------------------
We want to help you; help us to do it by reading FAQ222-2244 before you ask a question.

 

[cobmas]

Please check the program is properly compiled and stored in the correct Loadlib. After compilation please do
CEMT S PROG(ACCT01) NEWCOPY.

And then try. Hope this works

 

[ciczman]

HUJ,
From what I've read the problem is that you didn't add the new group to the start-up list(DFHLIST IBM's name). So when you recycled the CICS region the newly defined group is not recognized. When you did the install of the group and Newcopy (PHASEIN is better), you should see the new program with a length greater than zero(otherwise the program was linked to a different load library then represented in the DFHRPL concatenation or there's a mis-match of the program name/ID). Verify that!
To add the new group to the starup list, you have to identify the list name associated with the region. The name is identified in the overriding SIT parameter table. If you don't have a CICS SYSTEM PROGRAMMER, you can do a find on the CICS running job or output for GRPLIST. Normally the list name includes CICSxxxx. Once identified, sign onto the region and issue the CEDB EX L(CICSxxxx). This will expand the list. You can page forward to the end and issue an A G(goupname)next to the last group in the list or you can issue CEDA ADD GROUP(groupname) LIST(listname)on a blank screen after signing onto the region. This will ensure that the group will be defined to CICS when it gets recycled. NOTE- you don't have to recycle the region for a definition to be recognized to CICS. The Install makes it available to CICS and the NEWCOPY / PHASEIN loads the latest program object to CICS. Verify by issueing the CEMT I PROG(PROGNAME). CICS RDO manual

http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dfhjaa4f/CCONTENTS

 

[stevexff]

Suggest trying CEMT S PROG(nnnn) NEW to force CICS to load the module. This will either tell you the length, confirming it has been loaded, or give a failure message.

Unless you have a *really* old MVS, the block size thing doesn't matter any more.

The most likely thing is that you have a typo in the definition, your link-edit isn't working, or maybe that RACF won't let CICS load the module (in which case you should get an error message on the syslog).

Steve

 

[HUJ]

thanks all. i will try again!