With an XAUTOLOG followed by a SET SECUSER, you can still mis lots of error messages: surely all those caused by LINKs in the directory that fail, and possibly the first messages resulting from actions in the PROFILE EXEC.
I guess that a failing NICDEF (included in the CP directory) will just be like LINK: unnoticed when using XAUTOLOG#SET SECUSER. To see all problems resulting from directory statements, only 2 solutions - logon directly to the user - have you as secondary user on the user's CONSOLE statement and use XAUTOLOG (or have OPERATOR as secuser and look in OPERATOR's console log) Not even a COMMAND SPOOL CONS START in the directory will catch failing LINKs: the classic, old, directory statements are executed before the COMMAND statements. Replacing USER NICDEF ... LINK ... By USER ... COMMAND SPOOL CONS START COMMAND NICDEF ... COMMAND LINK ... will assure the errors are in de spooled console file 2008/10/9 Scott Rohling <[EMAIL PROTECTED]> > > How about the VM console log? I would want to see what messages are > occurring on the VM console when the guest starts up... > > Or to watch it: XAUTOLOG LINUX1 SYNCH#SET SECUSER LINUX1 * > > Or login directly to watch > > Scott Rohling -- Kris Buelens, IBM Belgium, VM customer support
