I've already done all of "
Setting up the ADCD package". For devices 0AA0-0AA2, this is what is in my devmap also listed below:
device 0AA0 3390 3390 # Available for dynamic mounts
device 0AA1 3390 3390 # Available for dynamic mounts
device 0AA2 3390 3390 # Available for dynamic mounts
# This file was generated Wed Jun 22 16:46:24 2022
# Volume directory: /home/ibmsys1/volumes
[system]
memory 14148m # 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 /home/ibmsys1/volumes/../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 --tunnel_ip=172.26.1.1 # QDIO mode
device 400 osa osa --unitadd=0
device 401 osa osa --unitadd=1
device 402 osa osa --unitadd=2
# DASD Devices are defined below. This list was derived from
# files in /home/ibmsys1/volumes
# 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,
# xxRES2, and xxSYS1 (case insensitive) were assigned 0A80, 0A81, and 0A82
# respectively.
[manager]
name awsckd 0001
device 0A81 3390 3390 /home/ibmsys1/volumes/A5RES2
device 0A82 3390 3390 /home/ibmsys1/volumes/A5SYS1
device 0A83 3390 3390 /home/ibmsys1/volumes/A5BLZ1
device 0A84 3390 3390 /home/ibmsys1/volumes/A5C551
device 0A85 3390 3390 /home/ibmsys1/volumes/A5C560
device 0A86 3390 3390 /home/ibmsys1/volumes/A5CFG1
device 0A87 3390 3390 /home/ibmsys1/volumes/A5DBAR
device 0A88 3390 3390 /home/ibmsys1/volumes/A5DBC1
device 0A89 3390 3390 /home/ibmsys1/volumes/A5DBC2
device 0A8A 3390 3390 /home/ibmsys1/volumes/A5DIS1
device 0A8B 3390 3390 /home/ibmsys1/volumes/A5DIS2
device 0A8C 3390 3390 /home/ibmsys1/volumes/A5DIS3
device 0A8D 3390 3390 /home/ibmsys1/volumes/A5IMF1
device 0A8E 3390 3390 /home/ibmsys1/volumes/A5INM1
device 0A8F 3390 3390 /home/ibmsys1/volumes/A5KAN1
device 0A90 3390 3390 /home/ibmsys1/volumes/A5PAGA
device 0A91 3390 3390 /home/ibmsys1/volumes/A5PAGB
device 0A92 3390 3390 /home/ibmsys1/volumes/A5PAGC
device 0A93 3390 3390 /home/ibmsys1/volumes/A5PRD1
device 0A94 3390 3390 /home/ibmsys1/volumes/A5PRD2
device 0A95 3390 3390 /home/ibmsys1/volumes/A5PRD3
device 0A96 3390 3390 /home/ibmsys1/volumes/A5PRD4
device 0A97 3390 3390 /home/ibmsys1/volumes/A5PRD5
device 0A98 3390 3390 /home/ibmsys1/volumes/A5USR1
device 0A99 3390 3390 /home/ibmsys1/volumes/A5USS1
device 0A9A 3390 3390 /home/ibmsys1/volumes/A5USS2
device 0A9B 3390 3390 /home/ibmsys1/volumes/A5USS3
device 0A9C 3390 3390 /home/ibmsys1/volumes/A5W901
device 0A9D 3390 3390 /home/ibmsys1/volumes/A5W902
device 0A9E 3390 3390 /home/ibmsys1/volumes/A5ZWE1
device 0A9F 3390 3390 /home/ibmsys1/volumes/SARES1
device 0AA0 3390 3390 # Available for dynamic mounts
device 0AA1 3390 3390 # Available for dynamic mounts
device 0AA2 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 172.26.1.2 TAP0
#
# DEVICE PORTB MPCIPA
# LINK IPAQENET PORTB
# HOME 192.168.1.xxx
#
# ; Routes section
# BEGINROUTES
# ROUTE 176.0.0.0 255.0.0.0 = TAP0 MTU 1492
# ROUTE 0.0.0.0 = MTU 1492
# ROUTE DEFAULT 192.168.1.1 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 127.0.0.53
# 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
# 192.168.1.xxx <your-zos-host-name> <your-zos-host-name>.<your-zos-domain-name>
# 172.26.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 , Device )
# OSATRL2E TRLE LNCTL=MPC,READ=(0404),WRITE=(0405),DATAPATH=(0406), X
# PORTNAME=PORTB, X
# MPCLEVEL=QDIO
#
# -- end of VTAM OSATRLx member
------------------------------
Mark Regan
Consultant, z/OS Network Software
Nationwide Insurance, Retired
Utica OH
------------------------------
Original Message:
Sent: Fri June 24, 2022 03:33 AM
From: Sebastian Welton
Subject: Can not get Ubuntu 21.04 Server to mount the USB Key
Did you check the PSW:
ExplanationFor initial program load (IPL), a volume has been loaded that does not contain IPL text.Operator responseCorrectly identify the correct volume to be loaded. Verify that the correct volume is mounted. If requested by the system programmer, obtain a stand-alone dump. ReIPL the system.
PSW Code 00F
I also see the following errors:
AWSDCK006W File name missing on device 0AA0AWSDCK006W File name missing on device 0AA1AWSDCK006W File name missing on device 0AA2
Presumably you have unencrypted the SYSRES volumes and changed permissions for all volumes.
Setting up the ADCD package
Sebastian
------------------------------
Sebastian Welton
Original Message:
Sent: Thu June 23, 2022 03:48 PM
From: Mark Regan
Subject: Can not get Ubuntu 21.04 Server to mount the USB Key
I tried another awsstart, but I get a "AWSEMI307I Warning! Disabled Wait CPU 0 = 00020000 00000000 00000000 0000000F" at the end of the start process. I was able to get two tn3270 ports started, but I was not able to do anything with them.
awsstart devmap --clean
IBM System z Personal Development Tool (zPDT)
Licensed Materials - Property of IBM
5799-ADE
(C) Copyright IBM Corp. 2007,2013 All Rights Reserved.
z1091, version 1.10.55.11, build date - 09/02/21 for Linux on Ubuntu 64bit
AWSSTA014I Map file name specified: devmap
AWSSTA090I All zPDT log files purged as requested
AWSSTA204I zPDT started in directory '/home/ibmsys1/volumes'.
AWSSTA146I Starting independent 1090 instance 'ibmsys1'
AWSEMI005I Waiting for 1090 license
AWSEMI314I CPU 2 zPDTA License Obtained
AWSEMI314I CPU 1 zPDTA License Obtained
AWSEMI314I CPU 0 zPDTA License Obtained
OSA code level = 0x7617
AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x400
AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x401
AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x402
AWSDCK006W File name missing on device 0AA0
AWSDCK006W File name missing on device 0AA1
AWSDCK006W File name missing on device 0AA2
AWSSTA059I System initialization complete
AWSSTA012I All configured subsystems started
$ ipl 0a81 parm 0a82CS
AWSMIP008I zArchitecture IPL mode (ZARCH_ONLY=ON)
$ AWSEMI307I Warning! Disabled Wait CPU 0 = 00020000 00000AWSEMI307I Warning! Disabled Wait CPU 0 = 00020000 00000000 00000000 0000000F
000 00000000 0000000F
------------------------------
Mark Regan
Consultant, z/OS Network Software
Nationwide Insurance, Retired
Utica OH
Original Message:
Sent: Tue June 14, 2022 03:01 AM
From: Sebastian Welton
Subject: Can not get Ubuntu 21.04 Server to mount the USB Key
I'm not quite too sure what you expect to see as that is all I see. Once you've installed the software including the license server then there are other commands as detailed in the ZD&T documentation which will allow you to interrogate the token and license server better.
Sebastian
------------------------------
Sebastian Welton
Original Message:
Sent: Mon June 13, 2022 03:51 PM
From: Mark Regan
Subject: Can not get Ubuntu 21.04 Server to mount the USB Key
This is for use with the the Learners Edition
The lsusb command can 'see' the device
Bus 001 Device 007: ID 04b9:8000 Rainbow Technologies, Inc. SafeNet Sentinel Hardware Key
But that's the only disk-related command that does.
I tried inserting it on a Ubuntu client, and it does not see it either.
------------------------------
Mark Regan
Consultant, z/OS Network Software
Nationwide Insurance, Retired
Utica OH
------------------------------