my current requirement is to change the TSO logon screen information. Initially, need to change in one of the LPAR( name of the LAPR is BIGIRON), later will implement the same in others.
I have figured out the assembler code which generates the message. SYS2.VTAMLST.Z113(USSSYT13).
code snippet:
000053,BIGIRON USSCMD CMD=BIGIRON,REP=LOGON,FORMAT=BAL
000054, USSPARM PARM=P1,REP=DATA
000055, USSPARM PARM=P2,REP=APPLID,DEFAULT=LP07TSO
000056, USSPARM PARM=LOGMODE,DEFAULT=D4C32XX3
000057, EJECT
....
....
000754,LN8 DC CL80'THIS SYSTEM IS MAINTAINED BY MIT Team'
and able to generate the load module, which is stored in SYS2.VTAMLIB.Z113(USSSYT13).
and in the console i ran this command.
/F VTAM,TABLE,OPTION=LOAD,NEWTAB=USSSYT13
getting error message VTAM not active.
Error message:
000080 ISF015I SDSF COMMAND EXECUTED ' F VTAM,TABLE,OPTION=LOAD,NEWTAB=USSSY
T13 ' SAKTHI TSOPRCDB TCP70023
000280 F VTAM,TABLE,OPTION=LOAD,NEWTAB=USSSYT13
000080 IEE341I VTAM NOT ACTIVE
Could someone help me out on this? how to activate the VTAM? Any help will be highly appreciated
since You qualify Yourself as Developer,
You have no business in doing the job of the system programming team.
more true since You did not care to research how thing are done in Your organisation
nor read the manuals on how to issue commands to the VTAM environment
google with IBM communication server manuals
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
Quote:
Could someone help me out on this? how to activate the VTAM? Any help will be highly appreciated
Unless you have suddenly become a system programmer, there is no reason for you to be doing this -- your site support group should be doing it. Scan your system log for IST messages -- if there are some there, VTAM is active, period. And if it is active, then the message you showed means the started task name is NOT VTAM but something else. What? Only your site support group (or someone working AT YOUR SITE) could possibly tell you that. There can be ramifications to changing the USS table (what VBUILD macros use the old USS table for example -- and if you don't know what I'm referring to, you should not be doing ANYTHING to USS tables). And unless the correct updates are made to VTAMLST, then you will have to repeat your change after every IPL from now on since VTAM will not keep them for you.
our system programmer third-party team's contract was expired, we are in the process of renewal. meanwhile, i got this urgent requirement. so I have to do it.
@Robert
thanks for pointing me the Task name error, it should be TN3270.
I have access to HMC console, i just stopped the TN3270 and restarted it.
I Do know its disruptive. so I did this on one of the LPAR which is accessed by few users.
For details you should look in z/OS V2R2.0 Communications Server: IP Configuration Reference, Chapter 12, Telnet USS table setup & Reference: Communications Server SNA Resource Definition Reference, Chapter 5, Unformated System Services Tables
