Configure CA Cloud Storage for System z Linux Server with two z/OS LPARs communicating with a CA Cloud Storage for System z server.
Follow these steps:
sudo cacloud setup root's password:
/usr/bin/setfacl -m g:cacloud:r /var/log/messages
This example adds the setfacl statement. Lines starting with '#' are comments.
# the firewall,acpid,NetworkManager log files
# are used by syslog-ng and rsyslog only, the
# other by all syslog daemons.
/var/log/warn /var/log/messages /var/log/allmessages /var/log/localmessages /var/log/firewall /var/log/acpid /var/log/NetworkManager {
compress dateext maxage 365 rotate 99 missingok notifempty size +4096k create 640 root root sharedscripts postrotate /etc/init.d/syslog reload /usr/bin/setfacl -m g:cacloud:r /var/log/messages <- Added line. endscript
}
An editor screen opens for the file /etc/cacloud/subsystems.conf. To change the port where the TCP/IP listener looks to accept connection requests from CA Vtape, use the following panel:
subsystem zos_xe72_svt1 0.0.1a00 0.0.1a01 subsystem zos_xe61_svt1 0.0.1a20 0.0.1a23
The order of the CTC addresses must match the order that is defined on z/OS. The CTC addresses can be the same on both sides of the connection.
Example of the InitSubsystems() section
InitSubsystems() {
##
## PURPOSE:
##
## Describe CTC connections to zOS client subsystem
##
## SYNTAX:
##
## subsystem os_sysname_svtn ctc ctc ...
##
## WHERE:
##
## os
## is the client operating system
## example: (ZOS, VM, DOS, LINUX, etc..)
##
## sysname
## is the sysname of the client operating system
## example: (LPAR1, LPAR2, XE61, SYSA)
##
## svtn
## is the svts subsystem running on that client operating system
## example: (SVT1, SVT2, SVT3, ...)
##
## ctc ctc, ...
## is a CTC device list used to communicate with the svts subsystem
##
## Each CTC device known to Linux is represented by a directory
## entry in sysfs. For CCW and CCW group devices the name used
## in the directory is a bus ID that identifies the device
## within the scope of a Linux instance. For a CCW device, the
## bus ID is the device's device number with a leading ?0.n.?,
## where n is the subchannel set ID.
##
## For example, 0.1.0ab1.
##
## CCW group devices are associated with multiple device numbers.
## For CCW group devices, the bus ID is the primary device
## number with a leading ?0.n.?, where n is the subchannel set
## ID.
##
##
## EXAMPLE:
##
## subsystem zos_xe72_svt8 0.0.1a00 0.0.1a01
## subsystem zos_xe61_svt8 0.0.1a20 0.0.1a21
subsystem demo_xe72_svt8 0.0.1a00 0.0.1a01 <-Modify these lines.
subsystem demo_xe61_svt8 0.0.1a20 0.0.1a23
}
You return to the Setup main menu.
The file FSTAB contains information about the read-only file systems.
/dev/disk/by-path/ccw-0.0.0200-part1 swap swap defaults 0 0 /dev/disk/by-path/ccw-0.0.0201-part1 / ext3 acl,user_xattr 1 1 /dev/disk/by-path/ccw-0.0.0202-part1 /usr ext3 acl,user_xattr 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 ip_address:/nfs_export_name /var/lib/cacloud/vault_01/mp_nn nfs rsize=131072,tcp,nolock,wsize=131072,intr,nfsvers=3
Indicates the IP address of the NFS device.
Indicates the mount point number.
You return to the Setup main menu.
The crontab file instructs the cron daemon to run this command at this time on this date. For more details type man crontab, 5, and press Enter.
## ## (Cron table entries used for cacloud ##
5 4 * * 1-6 test -x /usr/local/bin/cacloud && /usr/local/bin/cacloud --text scr_sync --live --verbose 2>&1 >> /var/lib/cacloud/reports/scr_sync # Run scratch sync Mon-Sat @ 4:05am 5 5 * * * test -x /usr/local/bin/cacloud && /usr/local/bin/cacloud --text mp_stats 2>&1 >> /var/lib/cacloud/reports/mp_stats # mountpoint stats daily @ 5:05am 35 5 * * * test -x /usr/local/bin/cacloud && /usr/local/bin/cacloud --text vol_stats 2>&1 >> /var/lib/cacloud/reports/vol_stats # Get volume stats daily @ 5:35am
## | | | | | | ## | | | | | +- command to be executed ## optional comments ## | | | | +---- day of week (0 - 6) (Sunday=0) ## | | | +------- month (1 - 12) ## | | +--------- day of month (1 - 31) ## | +----------- hour (0 - 23) ## +------------- min (0 - 59)
You return to the Setup main menu.
This command starts the Linux Server when the Linux system initializes.
cacloud-app-server on Start cacloud-app-server on boot, Y|N?
The CA Cloud Storage for System z server creates a log file as part of its ongoing operations.
This code is an example of the Scratch Sync log rotation instructions:
# Rotate cacloud logfiles
#
/var/lib/cacloud/reports/scr_sync {
nocompress
dateext
maxage 120
rotate 12
missingok
notifempty
size 4096k
create
sharedscripts
weekly
}
This example shows the SITEINFO information:
## Customer Information
CustomerInfo() {
##
## PURPOSE: Describe contact information
##
## CA Assigned Customer Site id, e.g. CUSTOMER_SITE_ID="12345"
CUSTOMER_SITE_ID="EVAL Site"
## CA Assigned Customer SAP Contract Number, e.g. CUSTOMER_SAP="CS4Z-12345"
CUSTOMER_SAP_CONTRACT="Unlicensed evaluation copy"
## The name of your company, e.g. CUSTOMER_NAME="CA Technologies"
CUSTOMER_NAME="Your Company Name"
## Customer contact information, e.g. CUSTOMER_CONTACT="John Doe"
CUSTOMER_CONTACT="John Doe"
## Customer contact email address, e.g. CUSTOMER_EMAIL="John.Doe@anycompany.com"
CUSTOMER_EMAIL="john.doe@mycompany.com"
## Customer misc notes, e.g. CUSTOMER_NOTES="Phone# (111) 222-3333"
# CUSTOMER_NOTES="uncomment to enter one additional line of information here"
}
You completed the setup tasks for CA Cloud Storage for System z Linux Server. The final customization task is to define the VOLSER ranges that match what you define on CA Vtape on z/OS.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|