Hi John,
The devmap is as follows. This was generated by create_devmap.pl. I have no error checked by awsckmap command.
Any advice would be appreciated.
# This file was generated Sun Oct 6 11:24:09 2013
# Volume directory: /z
[system]
memory 2167m # define storage size for virtual host
processors 3 # number of processors
3270port 3270 # port number for TN3270 connections
#ipl 0A80 "0A8200" # IPL command if automation required. See Redbook
#rdtserver 27000@tokenserver.yourcompany.com # required only for Rational tokens
#cpuopt zvm_couplingfacility
[manager]
name aws3274 0002 # define a few 3270 terminals
device 0700 3279 3274 mstcon
device 0701 3279 3274 tso1
device 0702 3279 3274 tso2
device 0703 3279 3274 tso3
device 0704 3279 3274 tso4
[manager]
name awsrdr 010C # define a card reader for job submission
device 00C 2540 2821 /z/../cards/*
# Network adapters are defined in the next two stanzas.
# Insure that the device addresses listed here correspond to the addresses
# listed in your VTAMLST definitions. Insure that the devices defined in your
# TCP/IP profiles and their associated VTAM definitions refer to the correct
# type of connection as listed by the find_io command.
# The "Wired" connection is for external network connectivity.
# The "Tun/Tap" connection is for connection to the driving Linux system.
# Sample configuration files can be found at the end of this generated device map.
[manager] # tap0 define network adapter (OSA) for communication with Linux
name awsosa 0009 --path=A0 --pathtype=OSD --tunnel_intf=y # QDIO mode
device 400 osa osa --unitadd=0
device 401 osa osa --unitadd=1
device 402 osa osa --unitadd=2
[manager] # eth0 define network adapter (OSA) for communication with network
name awsosa 0019 --path=F0 --pathtype=OSD # QDIO mode
device 404 osa osa --unitadd=0
device 405 osa osa --unitadd=1
device 406 osa osa --unitadd=2
# DASD Devices are defined below. This list was derived from
# files in /z
# Files with six character names that are greater than 800MB in size are
# assumed to be uncompressed DASD volume images. The first files named xxRES1
# and xxSYS1 (case insensitive) were assigned 0A80 and 0A82 respectively.
[manager]
name awsckd 0001
device 0A81 3390 3390 /z/HDC421
device 0AB0 3390 3390 /z/PUBLIC
device 0AB1 3390 3390 /z/USER00
device 0AB2 3390 3390 /z/SYSCFG
device 0AB3 3390 3390 # Available for dynamic mounts
device 0AB4 3390 3390 # Available for dynamic mounts
device 0AB5 3390 3390 # Available for dynamic mounts
#
# ==== END OF DEVICE MAP =================
# The following are sample TCP/IP definition statements for z/OS. These
# samples are based on your Linux configuration and some very simplistic
# assumptions about your network. These samples may be used as a
# starting point for creating your TCP/IP and VTAM definitions.
# -- start of TCP/IP PROFILE member (selected lines only)
# ...
# ; Device definition
# DEVICE PORTA MPCIPA
# LINK TAP0 IPAQENET PORTA
# HOME 10.1.1.2 TAP0
#
# DEVICE PORTB MPCIPA
# LINK ETH0 IPAQENET PORTB
# HOME 10.0.2.xxx ETH0
#
# ; Routes section
# BEGINROUTES
# ROUTE 10.0.0.0 255.0.0.0 = TAP0 MTU 1492
# ROUTE 10.0.2.0 255.255.255.0 = ETH0 MTU 1492
# ROUTE DEFAULT 10.0.2.2 ETH0 MTU 1492
# ENDROUTES
# ...
# ; Start section at bottom of TCP/IP profile
# START PORTA
# START PORTB
#
# -- end of TCP/IP PROFILE member
# -- start of TCP/IP TCPDATA member
# TCPIPJOBNAME TCPIP
# HOSTNAME <your-zos-host-name>
# DOMAINORIGIN <your-zos-domain-name>
# DATASETPREFIX TCPIP
# ; Define name servers with NSINTERADDR x.x.x.x
# NSINTERADDR 192.168.11.1
# RESOLVEVIA UDP
# LOOKUP LOCAL DNS
# RESOLVERTIMEOUT 10
# RESOLVERUDPRETRIES 1
# ALWAYSWTO NO
#
# -- end of TCP/IP TCPDATA member
# -- start of TCP/IP RESOLVER member
# GLOBALTCPIPDATA('USER.TCPPARMS(TCPDATA)')
# GLOBALIPNODES('USER.TCPPARMS(IPNODES)')
# COMMONSEARCH
# -- end of TCP/IP RESOLVER member
# -- start of TCP/IP IPNODES member
# 10.0.2.xxx <your-zos-host-name> <your-zos-host-name>.<your-zos-domain-name>
# 10.1.1.1 LINUX
# 127.0.0.1 LOCALHOST
# -- end of TCP/IP IPNODES member
# This sample defines the communications devices listed in
# the [manager] awsosa stanzas. This may reside in
# USER.VTAMLST(OSATRLx) or a similarly named location.
# -- start of VTAM OSATRLx member
# OSATRL1 VBUILD TYPE=TRL
# * Device for connection to Linux (CHPID A0, Device TAP0)
# OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402), X
# PORTNAME=PORTA, X
# MPCLEVEL=QDIO
# * Device for connection to network (CHPID F0, Device ETH0)
# OSATRL2E TRLE LNCTL=MPC,READ=(0404),WRITE=(0405),DATAPATH=(0406), X
# PORTNAME=PORTB, X
# MPCLEVEL=QDIO
#
# -- end of VTAM OSATRLx member
ibmsys1@rdt:~> awsckmap aprof
AWSCHK200I Checking DEVMAP file 'aprof' ...
AWSCHK204I Processed 141 records from DEVMAP /home/ibmsys1/aprof
AWSCHK208I Check complete, 0 errors, 0 warnings detected.
acky