Page 1 of 2

Cannot Start up CICS

PostPosted: Wed Oct 24, 2012 3:35 pm
by snkdbpc
I was assigned a task of creating a cics region, for that I was given a set of JCL which would create the following datasets,
ZCON317.CICS660.DFHAUXT
ZCON317.CICS660.DFHBUXT
ZCON317.CICS660.DFHCSD
ZCON317.CICS660.DFHCSD.DATA
ZCON317.CICS660.DFHCSD.INDEX
ZCON317.CICS660.DFHDMPA
ZCON317.CICS660.DFHDMPB
ZCON317.CICS660.DFHGCD
ZCON317.CICS660.DFHGCD.DATA
ZCON317.CICS660.DFHGCD.INDEX
ZCON317.CICS660.DFHHTML
ZCON317.CICS660.DFHINTRA
ZCON317.CICS660.DFHINTRA.DATA
ZCON317.CICS660.DFHLCD
ZCON317.CICS660.DFHLCD.DATA
ZCON317.CICS660.DFHLCD.INDEX
ZCON317.CICS660.DFHLRQ
ZCON317.CICS660.DFHLRQ.DATA
ZCON317.CICS660.DFHLRQ.INDEX
ZCON317.CICS660.DFHTEMP
ZCON317.CICS660.DFHTEMP.DATA
ZCON317.CICS660.SYSIN

I successfully created the above datasets, but when I try to start up the cics region (using /S ZCON317,START=INITIAL command), I get this error,
RESPONSE=ZTT1 IEE1321 START COMMAND DEVICE ALLOCATION ERROR


Further I tried to view the same in sdsf where I got the following message,

S ZCON317,START=INITIAL
$HASP100 ZCON317 ON STCINRDR
IEF695I START ZCON317 WITH JOBNAME ZCON317 IS ASSIGNED TO USER STC
, GROUP SYSPROC
$HASP373 ZCON317 STARTED
IEF403I ZCON317 - STARTED - TIME=09.57.24
-JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG
PAGE SWAP VIO SWAPS STEPNO
-ZCON317 ZCON317 CICS FLUSH 0 .00 .00 .00 0 0
0 0 0 0 1
IEF453I ZCON317 - JOB FAILED - JCL ERROR - TIME=09.57.24
-ZCON317 ENDED. NAME- TOTAL CPU TIME= .00 TOTAL
ELAPSED TIME= .00
-NOT_EXECUTED_STEP_TABLE BEGIN
-JOBNAME STEPNAME PROCSTEP STEPNO
-ZCON317 ZCON317 CICS 1
-NOT_EXECUTED_STEP_TABLE END
$HASP395 ZCON317 ENDED
IEE132I START COMMAND DEVICE ALLOCATION ERROR


Can anyone help me out with this?

Re: Cannot Start up CICS

PostPosted: Wed Oct 24, 2012 4:51 pm
by Robert Sample
If you look at the contest instructions, you will see that the first S xxxxxxx,START=INITIAL fails due to a missing file. You must create that file according to the instructions and then issue your S console command again.

Re: Cannot Start up CICS

PostPosted: Thu Oct 25, 2012 3:17 pm
by snkdbpc
I am unable locate the missing dataset :(..Tried to create the extrapartition dataset too but didn't work, any hint?

Re: Cannot Start up CICS

PostPosted: Thu Oct 25, 2012 7:51 pm
by dick scherrer
Hello,

Not my main area, but:
I am unable locate the missing dataset ..
Have you determined is this is supposed to already exist or if it is something your process should create?

Tried to create the extrapartition dataset too but didn't work, any hint?
As we mention over and over. . . Posting "it didn't work" is the Biggest waste of time and space on the forum. If something "does not work" you need to post what you tried and whatever undesired happened. Then, possibly, someone can help.

Re: Cannot Start up CICS

PostPosted: Fri Oct 26, 2012 11:43 am
by snkdbpc
I have explored a bit, and I think its due to DFHSIT, can anyone help me out with this?

Re: Cannot Start up CICS

PostPosted: Fri Oct 26, 2012 4:45 pm
by Robert Sample
DFHSIT deals with the CICS start up options. From the Messages And Codes (MAC) manual, this is the explanation of the IEE132I message:
4.77 IEE132I



--------------------------------------------------------------------------------

IEE132I START COMMAND DEVICE ALLOCATION ERROR



Explanation: A START command invoked a cataloged procedure. While allocating the device specified on the command, the system detected an error.
System Action: The system rejects the command.

Operator Response: Contact the system programmer. Enter the command again, as directed by the system programmer.

System Programmer Response: Do the following:



Look in the system output (SYSOUT) data set for messages associated with this START command. These messages describe errors found in the source JCL or in the overriding JCL statements generated from the START command.
If the MSGCLASS for Started Tasks is a DUMMY class, you may need to change it to a real message class temporarily in order to get the JES Job Log for the failing START command. Do this in one of the following ways:


Add the desired MSGCLASS to the START command. For example, add:



S procedurename,MSGCLASS=A


Change the MSGCLASS for all STCs using a $TJOBCLASS command, and then change the MSGCLASS back to what it was. For example:

First change the MSGCLASS using the $TJOBCLASS command:



$TJOBCLASS(STC),MSGCLASS=A


Now run the failing started task.

Finally, change the MSGCLASS back to what it was using a $TJOBCLASS command:



$TJOBCLASS(STC),MSGCLASS=Z





If the command fails again, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.

Once the failing JCL statements are identified, correct those JCL statements in the procedure or job, or any catalog entries which caused the error messages to be issued. Ask the operator to enter the command again.

If you read the quoted material carefully, you will find that the IEE132I message has NOTHING to do with CICS, nor the DFHSIT, but rather there is an error in the JCL -- such as the catalog shows a data set being on a particular volume but when the job runs it cannot locate that data set on that volume.

Re: Cannot Start up CICS

PostPosted: Fri Oct 26, 2012 10:45 pm
by snkdbpc
S procedurename,MSGCLASS=A

The command gives the following error,
RESPONSE=ZTT1
ICH408I USER(ZCON317 ) GROUP(SMCGRP ) NAME( MATT KOCKOTT )
JES2.MODIFY.JOBCLASS CL(OPERCMDS)
INSUFFICIENT ACCESS AUTHORITY
FROM JES2.MODIFY.* (G)
ACCESS INTENT(CONTROL) ACCESS ALLOWED(UPDATE )
$HASP690 COMMAND REJECTED - AUTHORIZATION FAILURE

Re: Cannot Start up CICS

PostPosted: Fri Oct 26, 2012 10:56 pm
by snkdbpc
Sorry, the command
$TJOBCLASS(STC),MSGCLASS=A

gives the above error,
The command S procedurename,MSGCLASS=A gives IEE132I error...

Re: Cannot Start up CICS

PostPosted: Fri Oct 26, 2012 10:57 pm
by Robert Sample
Did you try the ST command or the S command with MSGCLASS added?

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 12:48 am
by dick scherrer
Hello,

INSUFFICIENT ACCESS AUTHORITY
Have you corrected this?