#HDISV deployment modes and access methods

#Quick reference

• Overview
• Deployment modes
  • Managed service
  • Linux layer access
• Switching between modes
• Access examples
  • Connecting to Linux layer access instances
  • Connecting to Managed service instances

---

#Overview

HDISV provides two deployment options for users to choose from. This guide provides context for understanding which mode is right for a particular need or use case and how to access the z/OS environment in that mode.

#Deployment modes

#Managed service

Managed service provides a ready-to-use z/OS environment appropriate for a wide range of dev/OS use cases.

#Key features

• Ready-to-use z/OS - IBM-provided z/OS and middleware image
• Direct z/OS access - SSH and 3270 terminal to z/OS
• Software maintenance - Turn-key z/OS maintenance applied at user discretion
• User data preservation - User data persists when system instance is recreated
• Simple lifecycle - Easy to update, recreate, or expand storage

#Access methods

SSH to z/OS:

ssh zosadmn@<your-ip-address> -i ~/.ssh/id_rsa

3270 terminal:

• Connect to <your-ip-address> on port 2023
• Use any TN3270 emulator (IBM Host On-Demand, x3270, etc.)

TSO/ISPF:

• Login with username ZOSADMN
• Use the password set during initial setup

#Managed service lifecycle

Create:

• Order instance through ZLPN portal
• System is provisioned automatically
• z/OS starts and is ready to use
• 100 GB storage allocated (50 GB USER01 + 50 GB USMS01)

Recreate:

• Update to latest z/OS maintenance
• Option to change middleware selection (add/remove DB2, CICS, IMS)
• Option to switch z/OS versions
• User data is preserved (USER01 and USMS01 volumes)
• Same IP address maintained

Add storage:

• Order additional storage through ZLPN portal
• Mount available ordered storage space into system instance
• Format new space in z/OS

Terminate:

• Permanently deletes all user and system data
• Cannot be undone
• Back up important data first

↑ Return to Quick reference

---

#Linux layer access

Linux layer access provides full DevMap control for more complex setups and additional resources not available in Managed service mode. Linux layer access also allows import of existing environments for simpler migration between systems.

#Key features

• Linux system access - SSH to Linux layer as cloud-user
• Root access - Full system control via sudo
• z/OS access - Also includes SSH and 3270 to z/OS
• Complete flexibility and control - Customize everything, bring your own OS images

Important: Users are responsible for managing, configuring, all operating systems and software running in Linux layer access mode.

#Access methods

SSH to Linux:

ssh cloud-user@<your-ip-address> -i ~/.ssh/id_rsa

SSH to z/OS:

ssh zosadmn@<your-zos-ip-address> -i ~/.ssh/id_rsa

3270 terminal:

• Connect to z/OS IP on port 2023

#Important limitations

Cannot be recreated: Linux layer access instances cannot be recreated. The system cannot reliably preserve manual changes made to the Linux layer. To ensure a clean, consistent environment, Linux layer access instances must be terminated before a new instance can be created. All data is lost on termination, and custom configurations are not preserved.

#Linux layer access lifecycle

Create:

• Order instance through ZLPN portal
• Linux system is provisioned
• z/OS is installed and configured
• User receives Linux and z/OS IP addresses

Add storage:

• Order additional storage through ZLPN portal
• Configure the new space manually in Linux

Terminate:

• Permanently deletes all user and system data
• Cannot be undone
• Back up important data first

↑ Return to Quick reference

---

#Switching between modes

Important: It is not possible to convert an existing instance from one mode to another. Switching modes requires termination of the current instance and creation of a new one.

#To switch modes:

1. Back up data

   • Export datasets using FTP, SFTP, or dataset migration tools
   • Document any custom configurations
   • Save source code to version control

2. Terminate current instance

   • Use ZLPN portal to terminate

3. Create new instance

   • Provision new instance in desired mode
   • Restore data
   • Reconfigure as needed

Data loss warning: All data is lost when instance is terminated. Always back up important data before switching modes.

↑ Return to Quick reference

---

#Access examples

#Connecting to Linux layer access instances

Step 1: Connect to VPN

# Use VPN client to connect

Step 2: SSH to Linux

ssh cloud-user@<linux-ip> -i ~/.ssh/id_rsa

#Connecting to Managed service instances

Step 1: Connect to VPN

# Use VPN client to connect

Step 2: SSH to z/OS

ssh zosadmn@<zos-ip> -i ~/.ssh/id_rsa

Step 3: Set password

password_change.py -u ZOSADMN -p 'YourSecurePassphrase123!'

Step 4: Connect via 3270

• Open a 3270 emulator
• Connect to <zos-ip>:2023
• Login: TSO ZOSADMN
• Enter password

↑ Return to Quick reference