zPDT for VM

Commands

awsstart vm.dev

ipl 200 parm 0700

If it complains about checkpoint data you need to reply

oprmsg force

 

Getting ftp to work

logon to maint

to use netstat etc you need

cp link tcpmaint 592 592 rr

acc 592 p

To change the tcp config

cp tcpmaint 198 198 mr

acc 198 w

the tcp files are on the W disk

if you change the TCP config

logon TCPIP

press enter… read the messages

cp logon ftpserve

press enter – watch the messages

change profile tcpip

; uncomment portd 20 and 21

PORT
20 TCP FTPSERVE NOAUTOLOG ; FTP Server
21 TCP FTPSERVE ; FTP Server
23 TCP INTCLIEN ; TELNET Server

DEVICE DEV@0400 OSD 0001
LINK OSA0400 QDIOETHERNET DEV@0400

HOME

10.1.1.2 OSA0400
GATEWAY
; Network Subnet First Link MTU
; Address Mask Hop Name Size
; ————- ————— ————— —————- —–
10.1.1.1 255.255.255.0 = OSA0400 8992
DEFAULTNET 192.168.248.12 OSA0400 8992
; DEFAULTNET 9.19.40.1 OSA0400 8992
; (End GATEWAY Static Routing information)
; ———————————————————————-

START DEV@0400

_________________________________

 

You should now be able to ftp to 10.1.1.2
_______________________________________________
Understanding how it all works

in the AWSTART it defines

[manager]
name awsosa 0023 –path=A0 –pathtype=OSD –tunnel_intf=y
device 400 osa osa
device 401 osa osa
device 402 osa osa

the 400 is the address as seen by VM

When VM TCP starts up

system dtcparms has

.**********************************************************************
.* SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 3 May 2017
.* Configuration program run by MAINT640 at 17:27:20
.**********************************************************************
:nick.TCPIP :type.server
:class.stack
:attach.0400 AS 0001,0401 AS 0002,0402 AS 0003r

Which attaches external 0400 address as 0001  etc

The 0001 is used in

DEVICE DEV@0400 OSD 0001