Well, the problem was identified with Super Users in TSS. They get an
additional message I was not accounting for.
So the new ACLE for TPX looks like this
USERID SEARCH ' DS600306:'
BRANCH EQ,DISPATCH
STOP
DISPATCH MSG ' LOOKING FOR DISPATCH SIGNON FIELD'
* CLEAR
KEY 'LOGON'
ENTER ... SEND
KEY '&USERID'
ENTER ... SEND
KEY '&PSWD'
ENTER ... SEND
SEARCH 'VRDMI000' <=== NEW
BRANCH EQ,DONE <=== NEW
ENTER ... SEND
KEY 'CA'
ENTER ... SEND
*
* FINISHED WITH THIS LOGON
*
DONE STOP
Lizette
>
>Hi Liz,
> We have never had Dispatch defined in our ACT. We only have a profile
>definition for Dispatch to supply the ACB name. Each user is granted access to
>the profile via ACF2 and most all users are not allowed to to use a "/A"
>command.
>
>Our ACL is very simple and looks a bit like yours.
>
>* OPTION FLOW,ON *** DEBUG **
> OPTION MAXI,2000
>* OPTION TERM,ON *** DEBUG **
>* OPTION RESIDENT,ON
>*
> WAIT 2 WAIT 2 SECONDS
>LOOK1 SEARCH 'TASK CODE' SEARCH FOR THE PROMPT
> KEY 'HI &USERID' ENTER LOGON COMMAND
> ENTER
> WAIT 1 WAIT 1 SECOND
> SEARCH 'PASSWORD:' SEARCH FOR PSWD PROMPT
> BRANCH NE,DONE
> KEY '&PSWD' ENTER PASSWORD
> ENTER
>*
>DONE STOP WE'RE LOGGED ON NOW
>*
>
>Is this problem happening to a user that successfully gets in sometimes but
>not always?
>
>Could this be an issue with the pool of virtuals or the logmaode that they are
>picking up or possibly the term type on their TN3270 session (assuming they
>comming in via TN3270)?
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
