Sergio, The output will be handled the way your JES2 parms are setup for STCs. What I would do is use the command S CSQ6CHIN,MSGCLASS= and then specify your held queue. I realise that the CHIN maybe started by another process, so you may have to see if the parent that starts the CHIN can start it with the MSGCLASS= parameter.
Or you can start the CHIN manually (expecting issues) with the MSGCLASS just to check out the JCL. You can always start an STC without the parent process, just remember you may have other issues. But you will be able to see your JCL. Or you can just a TYPRUN=SCAN in a job card and execute the CSQ6CHIN in there. It will only allow the JCL to expand but you can see what may be incorrect. Lizette >Hello List, > > I have a process here, that START a Proc, and this Proc are resulted in > error. > I can look the Sysout, for try correct this, but, after the Job is > cancelled, I can find the Sysout output, in the SDSF command, > > Is here : > > - 06.52.01 s csq6chin > - 06.52.03 STC05927 $HASP373 CSQ6CHIN STARTED > - 06.52.14 STC05927 +CSQX005E CSQXJST Channel initiator failed > to - start > - 06.52.14 STC05927 IEF404I CSQ6CHIN - ENDED - TIME=06.52.14 > > > Looking at LOG command, the Sysout was Purged : > > +CSQX005E CSQXJST Channel initiator failed to start >0090 IEF404I CSQ6CHIN - ENDED - TIME=06.52.14 >0281 $HASP395 CSQ6CHIN ENDED >0281 $HASP250 CSQ6CHIN PURGED -- (JOB KEY WAS C1DAFD34) > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
