Logging back into AS/400
The question is very simple and I hear a lot of talk about nothing to do with the question asked...Please understand, I am not able to log in to get to the wrksplf or wrkjob queues. HOW DO YOU GET BACK ON AS400 SYSTEM ONCE YOU'VE LOGGED OUT? While trying to log back on, the system send this message "JOB ENDED ABNORNALLY". I can log into many sessions, but only one profile. Can anyone answer this????
Software/Hardware used:
AS400 ver 5.8 for windows
Software/Hardware used:
AS400 ver 5.8 for windows
ASKED:
March 26, 2011 9:01 PM
UPDATED:
May 3, 2011 6:50 PM
Answer Wiki:
Last Wiki Answer Submitted:
Be the first to answer this question.
All Answer Wiki Contributors:
Be the first to answer this question.
To see all answers submitted to the Answer Wiki: View Answer History.
this can be the job d or initial menu is not set correctly
HOW DO YOU GET BACK ON AS400 SYSTEM ONCE YOU’VE LOGGED OUT?
Generally, I tend to disconnect and reconnect rather than typre my profile/password into the Signon screen when I want to log back on. I have my sessions configured to “Bypass signon” in order to avoid the typing.
While trying to log back on, the system send this message “JOB ENDED ABNORNALLY”.
We will need to see the joblog for that job to know the reason given by the system.
I can log into many sessions, but only one profile.
I’m not clear on what that means. It seems to mean that you can start multiple sessions but can only logon using a single profile from that PC at during a given time. If you want to log off of one of those sessions in order to log on with a different profile, you see the “JOB ENDED ABNORNALLY” screen.
Is that close? If not, can you clarify?
Tom
@Zlevel
“I hear a lot of talk about nothing to do with the question asked”
I don’t believe either of the answers you’ve gotten are off-base at all. If you’d like to reply with some specific details to at least respond to the issues raised, then perhaps we could help you further.
To throw in my $0.02: I often see this error when users are in a program and close Client Access via the X in the top-right corner instead of signing out properly. When they attempt to reconnect, the system tries to join them back to the program, which by then may be dead already…hence, the crash.
Are you signing out (back to the sign on screen) as advised by your administrator when you close the Client Access program?
Each job you create on the system as 3 parts, the device AKA Job, user ID and unique number. This means that once a job ends it is completed as far as the system is concerned and you cannot restart a completed job. You can still work with spooled files and other things created by the old job by doing a WRKUSRJOB. This will show all jobs that are still on the system if they have any output associated with that job at all.
I hope this clarifies the answer
Lovemyi