A 'full-blown' GCS comes with a recovery virtual machine, often named 'GCS'.? It is supposed to perform storage cleanup if VTAM would abend.? If your GCS is generated this way, one must start the recovery machine first, other GCS members will refuse to start (probably what you see).? And, in such a case it would be common to have GCS perform the XAUTOLOG RSCS from its PROFILE GCS (and if working with VTAM, that PROFILE would start VTAM before RSCS, or maybe a CP SLEEP in the PROFILE GCS of RSCS so that VTAM is ready when RSCS tries to communicate with it.? A SLEEP i steh PROFILE GCS of GCS isn't a good idea I think: it would be unable to perform work during that time).
Another solution, for systems with RSCS and without VTAM, is to generate a "single member GCS group", only used by RSCS then.? No recovery machine required then.? I don't know by heart how to generate it.? The GCS manual will tell I guess.
As for RSCS console: it depends how ons issues the CP SPPOL CONS START.? If there is no TO xxxx parameter, the console is in the RSCS PRT queue: from MAINT: CP Q PRT RSCS ALL and then TRANS RSCS PRT nnnn TO *
Or get my LISTS package from the download library, there you'll find an URLIST EXEC what gives you a kind of RDRLIST for class D users; makes it easy to overlook the whole spool.? For example URLIST RSCS will display all file in RSCS' RDR, PUN and PRT queues.? You'd enter a TRANS / TO * to get the file in your RDR.
--
Kris Buelens
