probably you have a userprofile that has an initial job assigned to it, that is failing.
you can look at the job log to see the other messages associated with the error.
-Sarge
===================================================
You might need to review the joblog of the subsystem monitor job to see what the error was. I.e., if the subsystem is QINTER, then display the joblog of the active job named QINTER.
Tom
Last Wiki Answer Submitted: July 15, 2010 2:11 am by Rudedog950 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
I actually cannot log in. TCP/IP has been disabled and the console is the only terminal left from which I can possibly log in from. And that is where I am getting the error that will not allow me to login. So, I am not able to look at the job logs.
I actually cannot log in. TCP/IP has been disabled…
You will need a profile that can login. QSECOFR shouldn’t have a problem unless maybe a library in the system portion of the library list has been deleted… but that shouldn’t happen since you shouldn’t be able to delete a library when it’s in the library list of an active job and user libraries shouldn’t be in the system portion of the library list. QSECOFR shouldn’t have an initial program and should only use system defaults.
You might be able to login to DST at the system console. That should allow you to view and change settings.
TCP/IP might be disabled because the system portion of the library list is messed up. No normal jobs can start.
Of course, any diagnostic work assumes that you have a powerful enough profile that you can log on with!
Tom
I actually cannot log in. TCP/IP has been disabled and the console is the only terminal left from which I can possibly log in from. And that is where I am getting the error that will not allow me to login. So, I am not able to look at the job logs.
I actually cannot log in. TCP/IP has been disabled…
You will need a profile that can login. QSECOFR shouldn’t have a problem unless maybe a library in the system portion of the library list has been deleted… but that shouldn’t happen since you shouldn’t be able to delete a library when it’s in the library list of an active job and user libraries shouldn’t be in the system portion of the library list. QSECOFR shouldn’t have an initial program and should only use system defaults.
You might be able to login to DST at the system console. That should allow you to view and change settings.
TCP/IP might be disabled because the system portion of the library list is messed up. No normal jobs can start.
Tom