Page 2 of 2

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 10:38 am
by snkdbpc
I tried both, when I used 'S' I was getting the IEE132I error and when I used ST I got insufficient access authority.

And secondly, there was no SYSOUT dataset for this JCL

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 12:08 pm
by snkdbpc
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.


The question arises, from where shall I find this cataloged procedure that hasn't been allocated?

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 5:19 pm
by snkdbpc
Is there any command/procedure to list all the cataloged datasets?

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 6:16 pm
by Robert Sample
The question arises, from where shall I find this cataloged procedure that hasn't been allocated?
Sigh. Note that the error is NOT that the cataloged procedure is not being allocated, but rather a device (that is, disk volume most likely) is not being allocated due to a data set not being there (hence the JCL ERROR in your original post). Furthermore, JES has a list of datasets that it searches for procedures to execute when the START console command is issued. But you're not likely to have the authority to view that list.
Is there any command/procedure to list all the cataloged datasets?
Yes, but you are not likely to have authority to use it since listing all of the thousands of cataloged data sets in a system can require a large amount of resources. And nothing will tell you which, of those thousands of data sets, contains the one procedure you are interested in.

Have you allocated the application load library per the contest instructions? If so, what did you name it? If not, you need to allocate it, and the name MUST match the name in the start procedure. How do you find that name? Maybe ask someone involved in running the contest?

We have done all we can on this forum -- you need to work with the contest administrators from this point forward.

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 7:58 pm
by jaggz
Hi,
On insufficient authority - > Check with your security administrator to provide you the the Previlege of Starting the started task so which is usually controlled by OPERCMDS racf. Your Security administrator should be to able to help you. Once the security error is resolved , try to start the CICS region and check if it is coming up. Always Keep an eye on JESMSGLG and SYSLOG for more diagnostic information to troubleshoot.

HTH
Jaggz

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 8:05 pm
by enrico-sorichetti
the TS is partecipating to the zOS contest,

where the system is setup in a way that the losers have nothing to ask if they do things the way they should

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 8:06 pm
by jaggz
Hi,
If your Started task start up fails again due to JCL error, then you should check the CICS PROC. You have check each and every line of your CICS proc to make sure that those dataset exist or You need to make sure if you have created those Datasets. Incase if Symbolic representation in PROC is confusing then hardcode the value of CICS dataset and try starting it.

Jaggz

Re: Cannot Start up CICS

PostPosted: Sat Oct 27, 2012 8:13 pm
by Robert Sample
jaggz, I found a copy of the contest documents on the Internet. One of the steps in the third part is to start the CICS region by using a START console command -- the same one that is in the post that started this thread. The contest entrant is then explicitly told that the application load library does not exist and that is why the START command failed. The contest entrant must then allocate the application load library after which the START command will work.

Topic locked to prevent any further waste of our time on this useless thread.