Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
DOS n00b: how do I edit VTAMLST?
I'm working to get all of my Hercules systems talking to each other. I've got OS/390 speaking SNA to my other OS/390s on Hercules and my R/390s, so now it's time for next bit: getting VSE into the act. On OS/390, this is done by editing configuration members into SYS1.VTAMLST or a dataset concatenated to it. On VM, it's done by editing files on VTAM's 191 disk. On VSE, it's done by editing B books in PRD2.CONFIG. Is there a way to do that online, or do I have to create source members in an ICCF library and then run a batch job to update the real ones? Can I look at the existing members? Like I said, I'm a real DOS n00b... Jay Maynard |
Hi Jay,
Yes there is a way to do it online! In the interactive interface go to path 2 for Resource Definition. There you will find path 5 and 6, maintain VTAM Application Names and VTAM Startup Options. I have no experience with SNA networking, but this is where you should find the definitions you seek. If you also want to set up telnet, fast path 246 lets you define your VTAM logon table and terminal logmodes. If there's anything else I can do or if you get stuck, I'll try my best to help. |
Rene, that's the kind of interface I was looking for. Thanks! David, I'd seen the dialogs, but I'd prefer to have more control over the contents of VTAMLST, mainly so I can enforce my preferred naming convention. (VTAM guys love a good naming convention; it lets us figure out what's going on faster.) On Tue, Sep 14, 2021 at 8:49 AM René Ferland <ferland.rene@...> wrote: You can use DITTO. Logon to SYSA, escape to CICS and start DITTO, then navigate with the menus. --
Jay Maynard |
I'm planning to use VM VCTCAs to connect VSE VTAM to OS/390 and VM. I have the patched version with LCS SNA support running and talking on my LAN from one OS/390 to another. The goal is to get POWER's RSCS/NJE equivalent (PNET, right?) and VTAM applications and VTAM-owned terminals to talk anywhere?on my SNA network to any application running on any SNA-speaking OS on my LAN. I'll be using APPN connections in the absence of a license key for VM's VTAM to run in multisystem mode, since its client/server mode only does APPN. Does VSE VTAM support LCSs? If so, I might define up one of those, too. On Tue, Sep 14, 2021 at 12:38 PM Piotr Kolasiński <ptkola@...> wrote:
--
Jay Maynard |
to navigate to use esc to dismiss