Thanks
Susan
Susan, If no one offers any quicker solution, it would help to know whether you
(your authority) is key vs use of your PC.
What if you use your own userID at a twinax terminal? Are PC's able to go
then? What if you use someone else's ID at your PC? Are PC's still unable to
connect? Have you found that using your ID at any PC fixes things?
Can you get to the console before *ANY* PC connection attempt to determine if
there is an outstanding system message from the IPL?
Have you reviewed the joblog, system log, QSYSOPR message queue for clues?
Seems like there was something that passed thru here a month or so ago having to
do with authorities for server jobs which may apply here. But surely, there
would be a trace of such a problem in a log somewhere.
Sorry I can't help more...
Dick Daniels
http://www.wynth.com/
>We have terminals and PCs connected to our AS/400 via twinax. We are
>running V3R7 and most of the PCs are using Client Access for DOS. My
>problem is this:
>We do a backup every Friday night by calling a CL program. Once the
>backup is done it does a PWRDWNSYS command. When the system starts
>backup, the terminals can be turned on and any user can sign on with no
>problem. However, my PCs will not connect to the system, giving a
>message similar to "drive 'X' not assigned, 'system-name' not started,
>whenever a user attempts to turn the computer on and sign on. It
>requires that I must sign on with my authority. Once that is done I
>don't have to do anything else. I can sign off and all PCs will connect
>with no problems (until the next IPL) regardless of the user. Why? I'm
>new to AS/400 but somehow this doesn't sound correct. Because of this, I
>cannot do an unattended backup or IPL because I have to make sure that
>the PCs will connect before I walk out of the office.Any ideas?
>
>Thanks
>Susan
>
Try doing a STRTCP or a STRHOSTSVR *ALL. You're most likely not
starting these back up, which CA needs to run.
Also, make sure subsystem QSERVER is running. If these are the
problems, add them to your startup program. Put a delay in after the
STRTCP command before issuing STRHOSTSVR *ALL, though. About 60
seconds should suffice.
Bradley V. Stone
http://prairie.lakes.com/~bvstone
"Closing my my mouth before I scream. No one can shake my self-esteem." - YJM
i don't think that's the problem. didn't she say twinax and dos?
it sounds like it might be an authority problem. or it could be a licensing problem. or
the users may need to be enrolled in client access.... or something else....
so put on your detective hat..
key: dspmsg qsysopr and check the system operator messages. that may give a clue.
also key: wrksplf *all and check the system type messages. it may also say where why it
failed.
to check for authority, you could set up one of the other users with authority that
matches yours.
nj
I think Nina on the right track and I would look at what is happenning
with the QSTRUPPGM. It sounds as though one of the subsytems is not
starting. Perhaps QCMN is not starting except when you sign on with the
appropriate authority. Check the Log and QSYSOPR messages to see what
subsystems are starting and to see if all of the appropriate subsystems
are starting. Also check the log and QSYSOPR messages to see what
messages appear when you signon in the given situation.
Frank
Thank you for your help!!!!
Susan
Thanks again for your help.
susan
I did make one discovery that may help you or someone else help me with this
problem. This is what happens when I turn on a PC and it starts to boot up ... it
will ask for userID and password then go thru the steps of starting the systems. If
any other userID is used, I will then see these messages on the PC:
Starting Shared Folder Function
Assigning/Releasing Folders
5054 - System NODA Shared Folders program ended unexpectedly
(where NODA is our system name)
5049 - DRIVE I WAS NOT ASSIGNED TO A SPECIFIED SYSTEM
then the PC goes back to a c:>. If I reboot the PC and sign on with my ID then it
goes thru these steps with no problem and all PCs can then be accessed by any user.
In regards to the logs and message ques, I actually have not looked at them yet. I
am a novice on this system and unfortunately when I look at these I'm just not quite
sure what I am supposed to be looking for. Can you help?
Thanks so much!
Susan
Using WRKACTJOB, DSPLOG, DSPMSG QSYSOPR, DSPJOBLOG, and WRKOUTQ QEZJOBLOG, look
for words like 'MSGW', 'DLY-xxx', 'missing', 'authority', 'not available',
'missing', 'not started'...
I just spent some time trying to write instructions on how and what to look
for. (had some pretty good stuff, too!-) Decided to scrap it in favor of the
following...
(800) 237-5511 is the IBM support line number. This may be your best bet to get
this resolved. Also, you're welcome to call me... my hourly rates may be a
little lower. :-)
Good Luck!
Dick Daniels
http://www.wynth.com/
You know, it has been quite sometime since I've dealt with a
twinax-connected PC, but based on a few nano seconds of further thought,
I don't think a straight twinax-connected PC uses the QCMN subsystem
since it is not LAN connected. However I've included a sample output
from the command WRKACTJOB so you can see what subsystems should be
active, note that no TCP or Service Director components are started on
this system.
The key is to solving this is the system log and the QSYSOPR message
queue. Looking these can be a bit overwhelming because the system
documents so much and sometimes it will give you a message that looks
like an error but is not. Perhaps you could do a DSPLOG and prompt it
with an F4 and then enter the start date and time for your most recent
IPL. Look though this and look for suspicious messages that indicate a
failure to start something. "Can't allocate (XXXXX)" messages can be
ignored. Let us know what type of messages you find.
Regards,
Frank
Here is the WRKACTJOB data.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SUBSYSTEM
QBATCH QSYS SBS .0 DEQW
QCMN QSYS SBS .0 DEQW
QZSCSRVR QUSER PJ .0 ICFW
TR02 ENCORE EVK .0 * -PASSTHRU EVTW
QCTL QSYS SBS .0 DEQW
DSP01 QSECOFR INT .0 MNU-SAVE DSPW
QSYSSCD QPGMR BCH .0 PGM-QEZSCNEP EVTW
QINTER QSYS SBS .0 DEQW
TR02A ENCORE INT .0 CMD-WRKACTJOB RUN
QPGMR QSYS SBS .0 DEQW
QSNADS QSYS SBS .0 DEQW
XYZ QSNADS BCH .0 EVTW
QALERT QSYS SYS .0 DEQW
QDBSRVXR QSYS SYS .0 DEQW
QDBSRVXR2 QSYS SYS .0 DEQW
QDBSRV01 QSYS SYS .0 EVTW
QDBSRV02 QSYS SYS .0 DEQW
QDBSRV03 QSYS SYS .0 DEQW
QDBSRV04 QSYS SYS .0 DEQW
QDBSRV05 QSYS SYS .0 DEQW
QDCPOBJ1 QSYS SYS .0 EVTW
QDCPOBJ2 QSYS SYS .0 EVTW
QFILESYS1 QSYS SYS .0 TIMW
QJOBSCD QSYS SYS .0 EVTW
QLUR QSYS SYS .0 EVTW
QLUS QSYS SYS .0 EVTW
QPFRADJ QSYS SYS .0 EVTW
QQQTEMP1 QSYS SYS .0 DEQW
QQQTEMP2 QSYS SYS .0 DEQW
QSPLMAINT QSYS SYS .0 EVTW
QSYSARB QSYS SYS .0 EVTW
QSYSARB2 QSYS SYS .0 EVTW
QSYSARB3 QSYS SYS .0 EVTW
QSYSARB4 QSYS SYS .0 EVTW
QSYSARB5 QSYS SYS .0 EVTW
QSYSCOMM1 QSYS SYS .0 EVTW
SCPF QSYS SYS .0 EVTW
Susan Rossi wrote:
>
> Frank,
> Please excuse my inexperience. Can you tell me what ARE the appropriate subsystems that should
> be started after IPL? I could look a the messages but wouldn't know what I'm supposed to be
> looking for... unforunately. And if I do find something is not starting that should be, how do
> I start it? I'm new to all this and I just not confident yet about what to look for.
>
> Thank you for your help!!!!
> Susan
>
> Frank Healy wrote:
>
> > Susan:
> >
> > I think Nina on the right track and I would look at what is happenning
> > with the QSTRUPPGM. It sounds as though one of the subsytems is not
> > starting. Perhaps QCMN is not starting except when you sign on with the
> > appropriate authority. Check the Log and QSYSOPR messages to see what
> > subsystems are starting and to see if all of the appropriate subsystems
> > are starting. Also check the log and QSYSOPR messages to see what
> > messages appear when you signon in the given situation.
> >
> > Frank
> >