IBM Systems Lab Services and Training Quick-install of the ... · IBM Systems Lab Services and Training Quick-install of the Full System Copy Services Manager ... This is a quick-install

© 2015 IBM Corporation

[email protected]

ibm.com/systems/services/labservices

IBM Systems Lab Services and Training

Quick-install of the Full System Copy Services Manager

Version 7.70

Christian AaslandJune 2017

mailto:[email protected]

http://www.ibm.com/systems/services/labservices

© 2015 IBM CorporationIBM Systems Lab Services and Training – ibm.com/systems/services/labservices


2

What the heck is this document for?

This is a quick-install guide for configuring the Full System Copy Services Manager for

the following storage products:

DS8000 family (DS8000, DS8300, DS8870, etc)

SVC family (V3700, V5000, V7000)

Support for new XIV installations has been discontinued

Existing installations are still supported

Customers can have it, but it is designed to be performed by a Lab Services consultant

It does not explain details or how to handle errors or special/complex situations

Primary documentation is the FSFC Toolkit Wiki

Has more detail and explanations

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Advanced%20Copy%20Services/page/Full%20System%20Copy%20Services%20Manager%20%28FSCSM%29



3

Customer actions prior to our engagement

Configure the storage unit for Source, Target and Controlling LPAR's

LUNs

Host connections

Licenses (Flashcopy, Thin-provision, etc)

Provide the IBM i serial numbers so we can generate license keys

Source and Controlling LPARs configured with IBM i OS

Install the LPP's and PTF's on pages 5 and 6

Place FSFC Toolkit savefile IASHv7xx in QGPL on the controlling LPAR

We will send this to you before we arrive

DS8000 only:

Install DSCLI on the IBM i from the DS8K CD

Bundle 87.10.91.0 or newer (required for creating GMIR D-Copy)

Get IP addresses, administrative user IDs and passwords for:

HMC/FSM

LPAR's (including the target)

Storage devices

TPC-r Manager (if applicable)



4

Overview of Full System Flash Copy concepts

Fla

sh

co

py

Tape

Partition returns to

production duties

3

Flashcopy the disks

2

Backup the target

partition to tape

5

Write contents of memory to

disk

1

LPARs

IPL the target partition

4Source

Target

Source

Controller



Firewall access

Controller

Source

Target

BR

MS X

ferp

ort

*DFT = 5

50

66

Ping, ssh port 22

LPAR HMC (primary and secondary)

Pin

gTo

olkit (d

ft=83

72

)P

ing

Too

lkit (dft=8

37

2)

Rexec

(51

2) o

r D

DM

(44

6, 4

47

)In

stall: FTP (2

1)

Workstation access required for installation and configuration only

Pin

g, sshp

ort 2

2Teln

et 23

00

Ping, Telnet (23)



6

Controlling LPAR LPPs and PTFs

V5R4 6.1 7.1 7.2 7.3

5733SC1 *Base, 1

5733SC1 *Base, 1

5733SC1 *Base, 1

5733SC1 *Base, 1

5733SC1 *Base, 1

5722SS1 33,34 5761SS1 33,34 5770SS1 33,34 5770SS1 33,34 5770SS1 33,34

5722JV1 *Base, 6

5761JV1 *Base, 11

5761JV1 *Base, 11

5770JV1 *Base, 14

5770JV1 *Base, 16

Group PTF SF99291

Group PTF SF99562

Group PTF SF99572

Group PTF SF99716

Group PTF SF99725



7

Source LPAR PTFs

V5R4 6.1.0 6.1.1 7.1 7.2 7.3

Recent *CUMPKG

MF55941, MF46634, MF57128, MF54446, SI49221

MF55942, MF57124, SI49221

MF99006, MF56047, SI49487

If using BRMS, the following PTF’s are required (supercedingPTF’s are ok) :

SI48966 (BR1) SI48967 (BR1)

SI53859 (SS1)

SI64249 (BR1) SI53781 (SS1)

SI64248 (BR1) SI53860 (SS1)

SI64250 (BR1)

RED PTF's may require an IPL.



8

HMC Configuration (Click here if using FSM)

Create user qlpar on the LPAR HMCs

Hmcsuperadmin with AllSystemResources

Password is required (remember it for later!)



9

HMC Configuration

Enable remote command execution



10

HMC ConfigurationAllow ssh (port 22) through the firewall (on all adapters)



11

HMC Configuration

Secure Shell (port 22:tcp) must be allowed.

- Allow all hosts: 0.0.0.0/0.0.0.0

- Allow specified hosts: at least specify the IP of your controlling

LPAR



12

FSM Configuration

Create user qlpar on the LPAR FSM

–This may be a temporary password!

–Supervisor permissions

–Assign to Smadmin and smdefault user groups



13

Restoring, creating QLPAR, access codes on the Controller

Place the toolkit savefile in QGPL (FTP, scp etc)

scp IASHv770.savf user@hostname:/qsys.lib/qgpl.lib/iashv770.file

Restore the toolkit library from it:

RSTLIB SAVLIB(QZRDIASH5) DEV(*SAVF) SAVF(IASHV770)

The '770' refers to the release and may change

Create user profile QLPAR:

ADDLIBLE QZRDIASH5

GO TKMAIN

Opt 1 (Create QLPAR)

Opt 6 (Run setup)

ADDPRDACS ACSCDE(??)

The access code is based on serial number will be provided by the Lab Services consulting team



14

Download the Java Secure Channel code (on the Controller)

Download Java Secure Channel to /home/qlpar from

http://sourceforge.net/projects/jsch/files/jsch.jar/0.1.50/jsch-0.1.50.jar/download

Don't download a different version. It won't work.

The Java Secure Channel is an open-source implementation of ssh which allows the FSCS

Manager to issue ssh calls programmatically and to review the results.

Because it is open-source, IBM Legal requires that you download it yourself (i.e. we can't

bundle it with our toolkit)

Download to desktop, FTP to IBM I

Place in /home/qlpar/

ftp> bin

200 Representation type is binary IMAGE.

ftp> put jsch-0.1.50.jar /home/qlpar/jsch-0.1.50.jar

local: jsch-0.1.50.jar remote: /home/qlpar/jsch-0.1.50.jar

227 Entering Passive Mode (9,5,168,177,167,46).

150-NAMEFMT set to 1.

150 Sending file to /home/qlpar/jsch-0.1.50.jar

226 File transfer completed successfully.

249282 bytes sent in 0.742 secs (336.12 Kbytes/sec)

ftp>





15

Network settings:

Ability to ping the HMC/FSM and storage by name. If not, add host table entries

ADDTCPHTE INTNETADR('<HMC/FSM ip>') HOSTNAME((HMC/FSM hostname))

ADDTCPHTE INTNETADR('<storage ip>') HOSTNAME((storage hostname))

Recommend *LOCAL DNS lookups:

CHGTCPDMN HOSTSCHPTY(*LOCAL)

Verify a host name is set, and it can ping itself

Able to ping the source and target LPARs

OK if not on network, just ensure the IP resolved is correct

ADDSRVTBLE SERVICE('fsfc_dtaq_server') PORT(8372) PROTOCOL('tcp') TEXT('FSFC Toolkit Message Server')

Used for communications between the controller, source and target LPARs

Use any non-reserved (1024+) port you want

CHGSYSVAL SYSVAL(QRETSVRSEC) VALUE('1')

GO TKMAIN

Opt 2 (Generate SSH cryptographic key)

Opt 3 (Exchange SSH cryptographic key)

Use the IP address of the HMC

Enter the password for qlpar on the HMC

*SAVED is not valid

Recommend “Pause to view Java message” = 'Y' so you can see any errors.

Controller Network Configuration



16

Storage-Specific Setup

Click here for DS8000 setup

Click here for SVC setup



17

Create the environment – on the controller

WRKCSE

Option 1, type = FLASH

DS8K unit ID and IP, Flashcopy options and Source node name

Press “enter” when finished...

Change a FLASH Environment

Type choices, press Enter.

Environment name . . . . : FLASH9F9G1

Flash Copy DS unit information:

Device . . . . . . . . . IBM.2107-75AY031 Name

Flash Copy CS Manager options:

Full FlashCopy . . . . . *NO *YES, *NO

Resyncflash Copy . . . . *NO *YES, *NO

Space Efficient

FlashCopy . . . . . . *YES *YES, *NO

Target PPRC . . . . . . *NO *YES, *NO

System Node names:

Source Node . . . . . . CTCIHA9F Name

DS unit SMC information:

Flash hmc1 . . . . . . . 9.5.168.55 n.n.n.n

Flash hmc2 . . . . . . . n.n.n.n

More...

F1=Help F3=Exit F12=Cancel



18

Enter the source and target LUNs

Enter the volume ranges

Ensure the number of Volume Sets are correct

Add, Change or Delete Volumes

Environment . : FLASH9F9G1 Source device : IBM.2107-75AY031

Type . . . . . : FLASH Target device : IBM.2107-75AY031

Volume sets . : 2

Type Volume options; 1=Add, 2=Change, 4=Delete, press Enter.

CTCIHA9F Flash

Opt Volumes Volumes

1350-1351 1450-1451



19

Changing host connections

If you plan to change target host connections before activating the target LPAR, enter

this information with option 16

A Target LPAR pre-activation program is no longer needed

Define Host Connections

Environment . : FLASH9F9G1 Device . . . . : IBM.2107-75AY031

Type . . . . . : FLASH

Type Host Connection options; 1=Add, 2=Change, 4=Delete, press Enter.

Volume Target Node

Opt Group Host Connection

V5 003E

V5 0040



20

Configure communications with the DS8K

Communications with the DS8K uses password files, which we must configure.

ADDLIBLE QDSCLI

DSCLI SCRIPT(*NONE) HMC1('xxx.xxx.xxx.xxx') USER(qlpar)

PASSWORD(<temp password>) DSCLI(*int)

Run Copy Services (DSCLI)


Script: *NONE or name . . . . . > *NONE

Profile . . . . . . . . . . . . *DEFAULT

HMC1 . . . . . . . . . . . . . . 9.5.168.55

HMC2 . . . . . . . . . . . . . . *PROFILE

User . . . . . . . . . . . . . . qlpar

Password . . . . . . . . . . . .

Install Path . . . . . . . . . . '/ibm/dscli'

DSCLI CMD . . . . . . . . . . . *INT

Bottom



21

Set the password, create the password file

chuser -pw <new password> qlpar

chpass –expire 0

managepwfile -action add -pwfile /QIBM/Qzrdiash5/sec.dat -name qlpar -pw <new

password> -mc1 <SMC IP>

managepw MUST use an IP for the DS, not a name.

-action change can be used to update a password

> chuser -pw xxxxxxxx qlpar

Date/Time: November 14, 2014 9:35:13 AM CST IBM DSCLI Version: 7.6.31.133 DS: -

CMUC00134I chuser: User qlpar successfully modified.

dscli>

> chpass -expire 0


CMUC00195I chpass: Security properties successfully set.

dscli>

> managepwfile -action change -pwfile /QIBM/Qzrdiash5/sec.dat -name qlpar -pw xxxxxxxx -mc1 9.5.168.55


CMUC00207I managepwfile: Record 9.5.168.55/qlpar successfully changed in password file /QIBM/Qzrdiash5/sec.dat.

dscli>



22

Test the password file

DSCLI SCRIPT(*NONE)

PROFILE('/QIBM/Qzrdiash5/profiles/<EnvironmentName>_FLASH/flash.profile')

USER(qlpar) DSCLI(*INT)

Will provide a prompt to the DSCLI, where you can issue commands like lssi

Storage configuration is finished – continue with configuration

dscli>

> lssi

-,IBM.2107-75AY031,IBM.2107-75AY030,9B2,5005076307FFC2B8,Online,Enabled

-,IBM.2107-75AY032,IBM.2107-75AY030,9B2,5005076307FFCAB8,Online,Enabled

dscli>



23

SVC specific steps – Create SVC environment

Create a WRKCSE entry for the V7000 which will be referenced in the SYSCPY configuration

WRKCSE

Option 1, type = SVC

Enter the information for:

SVC Host Name or IP

Only one is supported

User and Password

Use an existing profile on the SVC or create a new one.

Consistency Group

Descriptive Text

Press F6 to validate the information

SVC Details


Environment . . . . . : FLASH9J9K

SAN Volume Controller Information:

Hostname . . . . . . . . ctchav7ka

User profile . . . . . . aasland

Password . . . . . . . .

Consistency Group . . . ctciha9j_ctciha9k

Text . . . . . . . . . .



24

Define SVC host connections if they are dynamic

Use the WRKCSE entry for the V7000 which you just created

WRKCSE

Option 16 on type = SVC

Enter the information for:

Virtual disk

Can be repeated if you want a disk attached to multiple host

Host name

Can be repeated if you want a host attached to multiple disks

WARNING: This will disconnect ALL volumes from these hosts

If you have longer name than fits in the field, use Opt 2

A target LPAR pre-activation program is not needed

Press F6 to validate this information

Storage configuration is finished – continue with configuration

Type Host Connection option, press Enter.

1=Add 2=Change 4=Remove 5=Display

Opt Volume Target host

ctciha9n_1_ls1 ctciha9n_sys






25

Configure the source LPAR – from the controller

From the controlling LPAR:

QZRDIASH5/CFGSRCLPAR

If this fails, check the following on the source LPAR:

FTP is running and the user profile specified can access it

The hostname is correct

The controller is reachable

Look in the log (dspf '/tmp/qzrdiash.log')

Configure source partition (CFGSRCLPAR)


Source LPAR host name . . . . . ctciha9j

User Profile . . . . . . . . . . QSECOFR User Profile

Password . . . . . . . . . . . .

Send library QZRDIASH5 . . . . . *YES *NO, *YES

Target release . . . . . . . . . *CURRENT Character value

Create user profile QLPAR . . . *YES *NO, *YES

QUSRBRM xfer port number . . . . *AUTO number, *AUTO

Create target LPAR line descri FSFCLINE *NONE, name

Create target TCPIP interface . 9.5.167.88

Create target TCPIP subnet mas 255.255.255.0

Toolkit access code . . . . . . 6B7CC7BB58



26

Configuring the source LPAR

All previous commands and messages:

250 Command SBMJOB CMD(CALL QZRDIASH5/QZRDIASTRP PARM('FTPSETUP'

'CTCIHA9L.RCHLAND successful

Enter an FTP subcommand

> quit

221 QUIT subcommand received

Starting setup program on CTCIHA9J.

Creating user profile QLPAR.

Setting authorities.

Registering license key.

Creating line description FSFCLINE.

Creating IP Interface 9.5.167.88.

Command completed with success.

Bottom



27

The next step is to create a simple configuration on the controlling LPAR

This will just do a Flashcopy, allowing us to get on the target LPAR to gather information.

QZRDIASH5/CRTSYSCPY

Create a configuration which:

Specifies the correct storagetype (*DS8K/*SVC)

Quiesces the source LPAR

Does not use BRMS

The first backup command is QZRDIASH5/ENDSYSCPY *PSTSAVSYS (it should always be this)

Does not configure network or tape devices

Does not call a target LPAR startup, exit or pre-activation target program

We will make it more complicated later … ;-)

Note the following:

HMC parameters are case-sensitive

Partition name

Partition profile

Managing system

Example:

CRTSYSCPY CONFIG(TEST7B7C) ENV(FLASH7B7C) SRCNAME(CTCIHA7B) SRCHMCLPAR('CTCIHA7B') SRCPROF('CTCIHA7B') SRCMNG(CTCIHA7) SRCPRIHMC('9.5.168.169') TGTNAME(CTCIHA7C) TGTHMCLPAR('CTCIHA7C') TGTPROF('CTCIHA7C') BACKUPAPP(*NATIVE) STGTYPE(*DS8K) TGTIPLSRC(B) TGTKEYPOS(*AUTO)

Create a simple configuration



28

Perform a flashcopy and bring up the target LPAR:

MKSYSCPY CONFIG(NEWCFG) USER(<user>) PASSWORD(<pwd>)

DDM is an option too, but adds more complexity. If you choose to use it, the profile which needs authentication to the source is qlpar

This configuration will not wait for the target LPAR to power up.

Installing the FSFC Toolkit – First FlashCopy (from Controller)

All previous commands and messages:

All environments successfully flashed.

Released lock on LPAR ctciha9j.

Acquired lock on LPAR ctciha9k.

Allowing 10080 minutes for ctciha9k to power down: 00000000

Partition ctciha9k is powered off.

All host connections changed successfully.

Partition ctciha9k activated.

Partition CTCIHA9J is online.

Partition CTCIHA9K is online.

Backups are finished.

Released lock on LPAR ctciha9k.

Flashcopy TEST9J completed with success.



29

After the target LPAR has IPL'd, log into the console

Get the TAPMLB serial number

WRKHDWRSC *STG

Option 7

Installing the FSFC Toolkit – Gather info from the target LPAR

CMB04 6B25-001 Operational Storage Controller

DC04 6B25-001 Operational Storage Controller

7 TAPMLB01 3577-000 Operational Tape Library

CMB05 6B25-001 Operational Storage Controller

Display Resource Detail

System: CTCIHA9J

Resource name . . . . . . . : TAPMLB01

Text . . . . . . . . . . . . : Tape Library

Type-model . . . . . . . . . : 3577-000

Serial number . . . . . . . : 78-78F1101

Part number . . . . . . . . :



30

On the controlling LPAR:

CHGSYSCPY (F4)

Add the tape info to your configuration

Configure the toolkit to use tape library

The “Backup device description” is the device description your backups expect to use.

The device serial number is the serial number from WRKHDWRSC *STG on the target LPAR. This is what the toolkit uses to find the resource name.

You can use either the media library or tape device serial number.

‘Robot Host’ and ‘Local internet address’ are for 3494 tape libraries

If there is no serial number reported, manually configure the media library by putting the following commands in the “backup commands” section:

VRYCFG CFGOBJ(T*) CFGTYPE(*DEV) STATUS(*OFF)

CHGDEVMLB DEVD(<devd>) RSRCNAME(<resource name>)

VRYCFG CFGOBJ(<devd>) CFGTYPE(*DEV) STATUS(*ON)

Change Full Sys Flash Copy (CHGSYSCPY)


Target LPAR Device Setup:

Backup device description . . 'TS3400' *SAME, *NONE, device name

Backup device serial number . '78-78F1101'

I/O bus . . . . . . . . . . . '*ANY' *SAME *ANY, number

Controller . . . . . . . . . . '*ANY' *SAME *ANY, number

Device . . . . . . . . . . . . '*ANY' *SAME *ANY, number

Robot host (3494) . . . . . . '*NOCHANGE'

Local IP address (3494) . . . '*NOCHANGE'

+ for more values



31

Get the communications adapter information

WRKHDWRSC *CMN

Option 7

If the serial number is all zero's (because it is a virtual adapter), use the location

Sign on to target LPAR and gather info

CMB11 268C Operational Comm Processor

LIN03 268C Operational LAN Adapter

7 CMN04 268C Operational Ethernet Port

Display Resource Detail

Resource name . . . . . . . : CMN04

Text . . . . . . . . . . . . : Ethernet Port

Type-model . . . . . . . . . : 268C-002

Serial number . . . . . . . : 00-00000

Part number . . . . . . . . :

Location : U8233.E8B.10001AP-V12-C3-T1



32

Add the communications information

CHGSYSCPY (F4):

Specify whether the identifier is a serial number (*SRLN) or location code (*LOC)

Enter the IP information for the target LPAR

If the target LPAR is on a different network, use the “Binding interface” parameter

to change the route

Finalize the configuration

Target Comm Interfaces:

Identifier Type . . . . . . . > '*LOC' *SAME, *SRLN, *LOC, *NONE

IO card identifier . . . . . . > 'U8233.E8B.10001AP-V12-C3-T1'

Line Description . . . . . . . > 'FSFCLINE' *SAME, *NEW, line name

IO card port number . . . . . > '0' 0-32

IO card IP interface . . . . . > '9.5.167.88'

Network Mask . . . . . . . . . > '255.255.255.0'

+ for more values

Target LPAR default route:

Binding interface . . . . . . > *NOCHANGE

Next hop . . . . . . . . . . . > ' '



33

CLNFSFCLOG will prune FSFC Logs to save on space

Tell it how many days of stuff to retain

Per configuration, *all, or *none (for core files only)

ADDJOBSCDE JOB(CLNFSFCLOG) FRQ(*WEEKLY) CMD(QZRDIASH5/CLNFSFCLOG CONFIG(*ALL) RETAIN(10)) SCDDATE(*NONE) SCDDAY(*ALL) SCDTIME('10:00')

Schedule Log Cleanup on the controller

Clean Full System Flashcopy lo (CLNFSFCLOG)


Configuration name . . . . . . . F4 to prompt

Days of information to retain . *NONE, days



34

Configure non-restricted state backup

Using CHGSYSCPY:

Set the USEBRMS to *YES then page down to see BRMS integration options

If BRMS, select the transfer method (*SAVF_SOCK is default, copies entire library)

Set the backup commands

For a non-restricted state backup, “wait for ENDSYSCPY” should be *NO



35

Test your configuration (non-restricted state backups)

Perform MKSYSCPY and verify your backups worked

It will take longer to perform verifications on the source LPAR with BRMS

The backups on the target will start, and BRMS will be sent to the source

You can sign on to the target HMC and monitor things

The controller will monitor the process

Run WRKMEDIBRM on the source when it is finished

It will appear as if the backups were performed on the source

Deal with any problems which come up, resolve them before proceeding to the next step.

The target log file is in /tmp/qzrdiash.log

The source log file is in /tmp/fsfc/<config name>/src.log

When the jobs finish, the logs are uploaded to the controller

Look in /tmp/fsfc/ for the logs



36

Create a configuration for restricted state backups

Create a new configuration based on your existing one

CPYSYSCPY oldconfig newconfig

Modify it to perform a SAVSYS backup Add the control group to run in the controlling subsystem

STRBKUBRM CTLGRP(SAVSYS) SBMJOB(*CTLSBS) Wait for ENDSYSCPY.... *YES

Do not IPL the LPAR after the backups.

Copy Full System Configuration (CPYSYSCPY)


Existing configuration name . . TEST9J F4 to prompt

New configuration name . . . . . SAVSYS9J Character value



37

Modify BRMS control group on the source LPAR - 1

Create a new (or use existing) control group on the source LPAR based on SAVSYS

Note the *EXIT's required in the control group:

QZRDIASH5/ENDSYSCPY ACTION(*PSTSAVSYS) ENDSYSCPY *PSTSAVSYS should be called from CHGSYSCPY as the first backup command.

SBMJOB CMD(QZRDIASH5/ENDSYSCPY) JOB(ENDSYSCPY) JOBD(QGPL/QLPARJOBD)At the very end, this will start TCP and notify the toolkit that backups are finished after QUSRBRM has been saved

For the test, consider not saving *ALLUSR, *LINK, and omitting user profiles from *SAVSYS

Just blank out the default activity fields

Add *SAVSECDTA to the *SAVSYS omits (F10)

Backup

Seq Items Exit command

10 *EXIT QZRDIASH5/ENDSYSCPY ACTION(*PSTSAVSYS)

20 *SAVSYS

30 *IBM

40 *ALLUSR

50 *ALLDLO

60 *LINK

70 *EXIT SBMJOB CMD(QZRDIASH5/ENDSYSCPY) JOB(ENDSYSCPY) JOB



38

Modify BRMS control group on the source LPAR - 2

Tell BRMS to NOT start the subsystems at the end of the control group

WRKCTLGBRM, opt 9

Necessary to allow backups in batch restricted state:

WRKPCYBRM *SYS, opt 1, Page Down

Seq Subsystem Library Option Delay Restart

10 *ALL *ALL *CNTRLD 30 *NO

Controlling subsystem:

Allow backups in batch . . . . . . . . *YES *NO, *YES

Restricted state time limit . . . . . *NOMAX 5-9999 minutes, *NOMAX



Run MKSYSCPY to test the configuration

LPAR reference code will be “A900 3C70” while in batch restricted state

Modify BRMS recovery reports

Insert custom message into the recovery reports to change system settings to start IP

STRSEU SRCFILE(QUSRBRM/QO1AUSRRCY) SRCMBR(STEP014)

Insert the following text: After restoring the configuration settings, run the following commands:CHGSYSVAL SYSVAL(QSTRUPPGM) VALUE('QSTRUP QSYS ')CHGLINETH LIND(ETHLINE) ONLINE(*YES)CHGTCPIFC INTNETADR('1.2.3.4') AUTOSTART(*YES)

CHGIPLA STRTCP(*YES)

Modify the recovery report creation to include the user info Add the parameter USRRCYINF(*ADD)

If STRMNTBRM is used to generate the reports

Modify the STRMNTBRM call with PRTRCYRPT(*NONE)

Add STRRCYBRM USRRCYINF(*ADD) to the job scheduler, to run 15 minutes (or so) after STRMNTBRM



40

Where can I find the logs for troubleshooting?

Logs are in the following places:

/tmp/qzrdiash.log

All LPAR’s

Contains non-MKSYSCPY actions

/tmp/fsfc/<config name>/

Controlling LPAR and Source LPAR

Contains following logs:- ctl.log MKSYSCPY’s log- src.log /tmp/qzrdiash.log from source LPAR- tgt.log /tmp/qzrdiash.log from target LPAR- CTL_*.log Joblog from MKSYSCPY- SRC_*.log Joblog from source LPAR- TGT_*.log Joblog from target LPAR

DMPINF FSFC(*YES) will grab all these files and put them in a zip file.

Log files are uploaded to the controller if the source and target programs run to completion.Ifthe programs do not finish, the logs will remain on the source and target until the next time they run to completion.

This means, in a failure, you may need to get logs from the source or target.



41

Contacting support if you have problems

Support for the FSFC Toolkit is to customers who meet the following criteria:

Current System i Software Maintenance Agreement

Current FSFC Toolkit Software Maintenance Agreement

For non-urgent issues or questions contact the consultant who installed the Toolkit. To reach a Toolkit developer for non-urgent issues and questions, or to report a bug, send an email to [email protected]

For immediate 24x7 assistance, reach out to IBM Support:

US: http://www.ibm.com/planetwide/us/

Worldwide: http://www.ibm.com/planetwide/

To assist IBM personnel in correctly routing your problem, request support for the iSeries

Lab Services “Copy Services Toolkit – Full System Flashcopy Only” using component

identifier 5798CST00.

Documents

IBM Systems Lab Services and Training Quick-install of the ... · IBM Systems Lab Services and Training Quick-install of the Full System Copy Services Manager ... This is a quick-install