RE: CPC1116 Cannot signon even from console - please help

[Jerry Adams <Jerry@xxxxxxxxxxxxxxx>]

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Terrence Enger
Sent: Monday, March 09, 2009 9:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: CPC1116 Cannot signon even from console - please help

<snip>
Jerry Adams suggests that library QGPL may be missing.  I think--well, I
hope--that would have provoked a different error message at the signon
screen.  You could check that by naming a known nonexistent library at
the signon screen.
</snip>

Terry,

You may be correct about a missing QGPL.  I ran a test on our dev system (which is running V5R4 so the results for V4R5 may be different).

First, I changed one of our user profiles so that the initial program, as defined on the user profile, did not exist.  When I tried to log in with that profile, I did not get an error message; rather, I simply got the panel:

                                   End of Job                              
                                                             System:   CROW
 Job:   D3             User:   ABILLING       Number:   243183             
                                                                           
 Job ended abnormally.                                                     
                                                                           
 Display the job log for more information.                                 

I looked at the job log, and its error messages was SYS5514 followed by CPF2494.  The SYS error, it appears, is because we run in the 36 environment per system values.  But, still, I had to look at the job log to see that; it was not on the display (again: V5R4 on a 520).  If I define a non-existent library in the user profile, I get the same panel, but a slightly different error message (SYS5552 - library not found).

The 36E on my box is certainly keeping me from getting the "normal" error messages, but, still, I could only see those when I looked at the job log.

The fact, as reported by Zvi, that he had no TCP/IP (which most of us start in the QSTRTUP program, at least I do) indicated to me that it was this program that was missing, not the user profile's startup.  Don't know if there are any options (C D I R) for the CPC1116 error, but, if there are, Zvi might try I, but this would mean, of course, that even if he can continue with the IPL, whatever was in the startup program would need to be done manually.  Frankly, this is hypothesis; I'm not able (or willing) to test this out on even our dev box!



Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email:  jerry@xxxxxxxxxxxxxxx