Thanks for reply . But I am not able to reach to TSO login stage. Even I am
not able to connect to session.


On Mon, Jun 16, 2014 at 12:12 PM, Michael Klaeschen <
[email protected]> wrote:

> For TN3270: In general there are two (or even three or more) logon steps
> to access TSO: last one of course is logon to TSO. Sometimes one has to
> use a session manager, then one needs to log on to ISZSMGR (or whatever)
> before. But here is the very first logon interesting. I have not seen an
> installation having it active. But it is still there: log on to TN3270
> server. That is the first access before (in general automated) choice
> which VTAM application to start. You should see something like "Enter Your
> Userid:", "Password: / New password:" and "Application:". Then, your
> TN3270 is all right. But you might want to check USSTCP parameter of
> TN3270's PROFILE DD. Sometimes, there are INTERFACE or DEVICE names given
> which might include your old SMF system identifier. In that case, your
> well-known logon application is not shown and you'll have to start VTAM
> application for TSO logon manually.
>
> In case you really have problems to logon to TSO itself, then of course
> there are numerous reasons available. Think of issues like forgotten
> password, wrong REGION size, typo in logon procedure name...of course
> everyone of us (including me) is aware and there is definitely no need at
> all to double or even triple check this. Did you check the VTAM generic
> resource naming for TSO together with RACF APPL class? One common practise
> is to include SMF system identifier in the profile names. When you forgot
> to change them, no MVS identity will be allowed to access TSO on that
> system. You might have luck with UADS.
>
> Just two thoughts on this topic. There might be many many more items to
> consider. More or less guessing...
>
> Cheers
> Michael
>
>
>
> Von:    Mainframe Mainframe <[email protected]>
> An:     [email protected]
> Datum:  2014-06-16 08:00
> Betreff:        TN3270 Issues
> Gesendet von:   IBM Mainframe Discussion List <[email protected]>
>
>
>
> After Changing system name , IPLed system and VTAM, TCPIP, TSO,TN3270 all
> cameup, but I still not able to login to system.
> I tried pining IP connected to my system and I am able to ping.
>
> but I am not able to isolate why I am not able to access tso. I dont see
> any messages on console related to this. I still feel TN3370 has some
> issue
> but not sure 100%.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
>
> Basler Sachversicherungs-AG
> Amtsgericht Bad Homburg v.d.H., HRB 9357 | USt-ID-Nr. DE 276021973
> Basler Straße 4, 61345 Bad Homburg v.d.H.
> Vorstand: Jan De Meulder - Vorsitzender, Markus Jost, Dr. Jürg
> Schiltknecht, Dr. Alexander Tourneau, Dr. Christoph Wetzel
> Aufsichtsratsvorsitzender: Dr. Martin Strobel
>
> Basler Lebensversicherungs-AG |
> Amtsgericht Hamburg, HRB 4659 | Ust-ID-Nr. DE 276021973
> Ludwig-Erhard-Straße 22, 20459 Hamburg
> Vorstand: Jan De Meulder - Vorsitzender, Markus Jost, Dr. Jürg
> Schiltknecht, Dr. Alexander Tourneau, Dr. Christoph Wetzel
> Aufsichtsratsvorsitzender: Dr. Martin Strobel
>
> Basler Versicherung AG Direktion für Deutschland |
> Amtsgericht Bad Homburg v.d.H., HRB 1228 | USt-ID-Nr. DE 281452875
> Basler Straße 4, 61345 Bad Homburg v.d.H.
> Hauptbevollmächtigter für Deutschland: Jan De Meulder
>
> Basler Leben AG Direktion für Deutschland |
> Amtsgericht Bad Homburg v.d.H., HRB 1229 | Ust-ID-Nr. DE 281452875
> Basler Straße 4, 61345 Bad Homburg v.d.H.
> Hauptbevollmächtigter für Deutschland: Jan De Meulder
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to