HSM Components The main HSM components are illustrated below.
The white boxes are the data functions, the yellow ellipses are the control datasets, the blue boxes are the data stores, and the green boxes are the recovery logs and trace datasets.
Migration Backup and Migration are the two main functions of HSM.
HSM recognises data in three places. ML0 (Migration level 0 is the on!line data that is accessed by applications and users. "ata is usually moved to ML1 (Migration level # first, according to SMS management class rules. M$# is a dedicated pool of dis%s, which are non!SMS managed. The data is compressed. The minimum si&e a dataset can be is about ') (assuming *0 trac% geometry. Small datasets could be archived to M$#, but still use the same space, so small datasets are held as records in Small "ata Set +ac%ing datasets (S"S+s. These These are standard )S"S )S"S S-M S-M files. To use small dataset pac%ing, you have to tell "HSM how big a small dataset is. /ou /ou need an entry in your -11M"xx dataset li%e
SETSYS SMALLDATASETPACKING(KB(160))
-s a guide, a single trac% record record using half trac% bloc%ing, and getting getting 2# compression will will use about #30)4 on M$#. 5f all these assumptions are correct for your site, then #30)4 is a reasonable cutoff point, as anything smaller would not occupy a whole trac%. 5f a dataset continues to be unused, it will eventually be migrated off to ML2 (migration level 6, which is usually high capacity cartridge. $arge datasets are often migrated straight off to M$6. Migrated datasets are given a special catalog entry, with a volser of M57-T, M57-T, to indicate that the dataset is migrated. The M1"S (Migration 1ontrol "ata Set %eeps a record of what has been migrated, and
where the migrated data is held. 5f you try to access a migrated dataset, it will be automatically recalled bac% to M$0. There are three variations of space management
Primary Space Management To run primary space management you need to issue commands li%e these
DEFINE PRIMARYSPMGMTCYCLE(YNNNYNN) CYCLESTARTDATE(2004/03/01) SETSYS PRIMARYSPMGMTSTART(0100 0300)
This means run primary space management on Mondays and ridays, starting at 0#200. HSM will not start to process any new volumes after 0200. The reason why it starts on a Monday is because March #st 6008 was a Monday. Monday. /ou /ou would typically enter this command once when setting up HSM, and then 9ust enter it again if you wanted to change the parameters. parameters. +rimary space management does all the space management functions on the primary, or M$0 dis%s. 5f allowed by parameters, it will delete temporary and expired datasets, release unused space, then migrate data to M$# or M$6 as appropriate, until all volumes are below their SMS thresholds.
Secondary Space Management Secondary space management needs an initial command, similar to primary space management. 5f you never enter this command, then secondary space management will never run.
DEFINE SECONDARYSPMGMTCYCLE(YNNNYNN) CYCLESTARTDATE(2004/03/01) SETSYS SECONDARYSPMGMTSTART(0030 0200)
Secondary space management basically loo%s after the M$# and M$# archive pools. 5f the management class criteria are met it moves data from M$# to M$6, it runs T-+:1;+/ commands commands if they are needed and it deletes expired migrated datasets. The end of that last sentence needs a bit of expansion. HSM can delete migrated datasets, that it it can delete data once it is not re/ and the HSM parameter ?Scratch expired "ata Sets? must be set to /:S. 5f it is not, change it with command
HSEND SETSYS EXPIREDDATASETS(SCRATCH)
Interval Migration /ou /ou run interval migration on one $+-, $+-, so for that $+- you specify
SETSYS INTERVALMIGRATION SETSYS MAXMIGRATIONTASKS()
in the -11M"xx +armlib member, and in all other $+-s you specify
SETSYS NOINTERVALMIGRATION
5nterval migration runs every hour, and chec%s each volume occupancy against the SMS threshold settings for the volume?s storage pool. 5f the high threshold is exceeded, then "HSM will migrate eligible datasets until the low threshold is reached or no more data sets are eligible. 5t will also delete temporary and expired data sets
Automatic Recall /ou /ou can restrict the number of recall tas%s with the follo wing S:TS/S parameter.
SETSYS MAXRECALLTASKS(!2) TAPEMAXRECALLTASKS(!1)
The tape recall tas%s are a subset of the max recall tas%s, so n# must be smaller than n6.
back to top
Backup "ata needs to be bac%ed up on a regular basis, incase it is accidentally deleted or corrupted. Hardware failure is very rare these da ys. HSM can stage bac%ups to M$#, or write them straight to tape. 4ac%ups are recorded in the 41"S (4ac%up 1ontrol "ata Set. This ma%es recovery very easy. The ;1"S (;ffline 1ontrol "ata Set %eeps a record of all tapes used by HSM, both bac%up and migration. To schedule schedule HSM bac%ups to run automatically, you need to add lines li%e these to your -11M"xx -11M"xx member
SETSYS A"TOBACK"PSTART(0100 0200 0600) SETSYS MAXBACK"PTASKS(3)
@hat this says is that the bac%ups will start between 0#200 and 06200, and no new volume bac%ups will start after 03200 Ap to three concurrent bac%up tas%s can run on this host. 5f you are running in a sysplex with several $+-s, its best to run several concurrent bac%up tas%s from a single $+-, rather than spreading the tas%s between $+-S. $+-S.
Log & PDA fles The 1"S files are critical to HSM, so updates to them can be logged. 5f a 1"S fails, it can be recovered from bac%up, then the log updates applied to get it bac% to the point of failure. The +"- (+roblem "etermination files are trace datasets. The 1"S ecovery section explains how the logs can be used to fix 1"S errors.
bac% to top
HSM Dataset Level Commands These commands can be used by non!authorised users (users who are not "HSM administrators when prefixed with an ?H?. -uthorised users can also use them without the ?H? if they are preceded by HS:=". or example HS:=" $5ST "S=-M:(my.file 4;TH will give the same result as H$5ST "S=-M:(my.file 4;TH 5 find the ?H? commands very useful as line commands from TS; option .8. /ou enter the command on the left hand side of the dataset you want to action, and 9ust use a ?B? where you would normally have to type in the dataset. TS; will substitute the dataset name for the B in the commands. The "ataset Tips section Tips section contains a number of examples of these commands in action. @hen you loo% at a list of datasets under TS; .8, migrated volumes are shown with a dis% entry of M57-T# M57-T# if they are on M$#, or M57-T6 M57-T6 if they are on M$6. @hen you issue the command ?S;T ;$AM:? on the command line this only sorts on the first 3 characters of the ;$AM:, so if you want to sort migrated datasets you can get M57-T# and M57-T6 datasets mixed together. To get round this problem you have to enter the command ?S;T ;$AM: M;$? on the command line. This will cause a sort of the volume and also the ?Multivolume or Migration $evel indicator?. Many "HSM commands echo the results to your terminal by default. 5f you enter a command and see no result, then "HSM probably wrote the result to the "HSM log file. 5f you add the parameter ?T:M? to your command, it will echo the result to your console. 5f you want to save the command output, you can add the parameter ;"S(file.name to redirect the output to a file. The file must not exist, as "HSM will allocate it. /ou can also send the results to the spool with S/S;AT(class S/S;AT(class
LIST command The $5ST command has a lot of parameters that ma%e it useful for finding out information about bac%ups or migrated files. 5t is easiest to use as a line command on 5S+ option .8 as shown below.
HLIST DSNAME(/) BOTH HLIST DSNAME(/) MCDS HLIST DSNAME(/) BCDS
Typical Typical results of these commands are
DSN#$%&%'&!% * DSN#$%&%'&!%* MIGVOL#A+3,40 DSO#PS SDSP#NO LAST REF#0-/02/11 MIG#04/02/1, TRKS#001042 2K BLKS# ....... TIMES MIG# 001 16K BLKS#031332 LAST MIGVOL#.NONE. DSN# $%&%'&!%*
BACK FRE+ # ...
BDSN#HSMBACKT-110,$%&%'&! BDSN#HSMBACKT -110,$%&%'&!%*40%*40BACKDATE#0-/02/ 2 BACKTIME#0,11 BACKDATE#0-/02/2 BACKTIME#0,11 CAT#YES RACF IND#NO BACK PROF#NO
MAX VERS#...
BACKVOL#A+3-2, FRVOL#DS003E GEN#000 VER#001 "NS/RET# NO
5f you also wanted information about datasets that have not been migrated, then add the 5=1$A": +5M-/ parameter. parameter. This will then give you details about files that have been migrated and recalled. The list command will also give you lots of information about "HSM ob9ects. Here are a few examples
LIST BACK"PVOL"ME LIST BACK"PVOL"ME('5) LIST BACK"PVOL"ME SELECT(EMPTY)
The first command will list out all bac%up volumes, the second one will list out data for a selected bac%up volume, while the third command will list out all empty bac%up volumes. To list out all the migrated files held on a tape. 5ts best to direct the output of this command into a file, as there will be lots of it. /ou may need to do this if the tape is bro%en, to see what you have lost. The information is held in the ;1"S, so you do not need to mount the tape. 5f you want to list out one volume, but do not want the migrated files list, use the parameter =;"-T-S:T5= =;"-T-S:T5=;M;M-T5;= T5;= to suppress the list.
HSEND LIST TTOC(A+10-6) ODS('&7&87&9!%*)
5f you specify TT;1 without a ;$S:, then HSM will list out a summary of all of its tapes, but it will not list out all the individual files on the tapes. 5f you want to list out all your disaster recovery migration tapes, maybe for a "r test, then use the command
HSEND LIST TTOC SELECT(DISASTERALTERNATEVOL"MES)
To list out the contents of a small dataset pac%ing dataset on an M$# volume use the command below. /ou /ou can also see all the files on an M$# volume with S:$:1T(;$AM:(volser S:$:1T(;$AM:(volser M$#
HSEND LIST DATASETNAME MIGRATIONCONTROLDATASET : SELECT(VOL"ME(ML102-) SDSP) ODS('&7&87&9!%*)
/ou /ou can also filter out a set of migrated datasets with the level parameter. The command below will lost all migrated datasets with high level
HSEND LIST LEVEL(C+PY) MIGRATIONCONTROLDATASET ODS('&7&87&9!%*)
$ist the "HSM characteristics of a primary volume. =ote the T:M parameter. The $5ST command sends it?s output to the HSM log by default.
TSO HSEND LIST PVOL(D3003-) TERM
results
VOL#D3003- DEVTYP#33 DEVTYP#33,0 ,0 VOLTYPE#P SMS MIGDS#00000 MIGDS#000 00 MIGTRKS#. MIGTRKS#...... ..... MIGDATE:TIME#04/03 MIGDATE:T IME#04/03/01 /01 1312 FRAG#6- HI:THRESH HI:THRESH#0- #0- LO:THRESH LO:THRESH#060 #060 MIN:AGE#... BACK"P:DEVICE:CA BACK"P:DEVICE:CATEGORY#.... TEGORY#.... A"TO:RECALL#. SDSP#... SPACE:MGMT#MIG AGE#... A"TO:HOST MIG#.. BACK#.. D"MP#.. D"MPCLASS # ........ ARC0140I LIST LIST COMPLETED; COMPLETED; LINE(S) OF DATA O"TP"T O"TP"T ...
To list out all the bac%ups for files that match a partial dataset name use
HSEND LIST LEVEL(8%5&%$'!%*) BCDS ODS(9!%*)
/ou /ou can also filter down a large HSM li st using the S:$:1T parameter. -s -s an example
HLIST LEVEL(RSPROD) SELECT(AGE(10 0)) MCDS TERM
will list out all migrated datasets starting with SD+;" that have not been referenced f or less than #0 days, or more than '0 days. =ote that the $::$ statement does not have to be a complete
HSEND LIST PVOL('5) BCDS BACK"PCONTENTS ODS(9!%*)
The $5ST TT;1 command can ta%e some special S:$:1T filters, including S:$:1T(4-1)A+ =;TA$$, which will show all bac%up tapes that are not full, and S:$:1T(=;T-SS;15S:$:1T(=;T-SS;15-T:" T:" which will list all tapes that are not associated with an HSM function. /ou /ou can list out "AM+ ob9ects as shown below. 5f you do not specify a particular class or volume, then all classes or volumes will be listed out.
LIST D"MPCLASS(<%'') LIST D"MPVOL"ME('5)
BACKUP Commands HAC!DS Command /ou /ou use this command to manually bac%up a dataset. /ou /ou may want to do this before you ma%e changes. The .8 line command can simply be
HBACK /
/ou /ou will have a default bac%up destinationF use the CA:/ S:TS/S S:TS/S command to find out what i t is. /ou /ou can override this as in the following example. This example will also use concurrent copy for the bac%up ?11? means 1oncurrent 1opy, ?:CA5:"? ?:CA5:"? means the bac%up will fail if it cannot use concurrent copy, and ?$:? means the bac%up will be considered complete once the concurrent copy is established, rather than when all the data is copied off to tape.
BACKDS 9!%* TARGET(DISK) CC(RE+"IRED LE)
HR"C#$"R Command
/ou /ou use this command to restore a data set from the bac%up. rom 5S+ option .8, this can simply be
HRECOVER / REPLACE
-nd hopefully you will see
ARC0-I DATA SET 5<5$9!% 5<5$9!%* * =AS RECOVERED FROM A BACK"P MADE AT ARC0-I (CONT) 0,11 ON 2004/02/2 ARC1000I 5<5$9 5<5$9!%* !%* RECOVER PROCESSING ENDED
/ou /ou can recover a file to a different name, and select a bac%up ta%en on a specific date with the following TS; command
HSEND RECOVER 5<5$9!%* NE=NAME(5<5$9!%*!>!%*) : DATE(,,/11/04)
This command will recover a file to a new name, and force it onto a non!SMS volume
HSEND RECOVER 5<5$9!%* NE=NAME(5<5$9!%*!>!%*) : TOVOL"ME(V00101) "NIT(33,0) FORCENONSMS
HD"L"T" Command 5f you want to delete a lot of bac%ups, you will want to batch them up and run them as a 9ob. @hen you do this, "HSM will issue all the commands at once and
HSEND HSEND HSEND HSEND
=AIT =AIT =AIT =AIT
BDELETE BDELETE BDELETE BDELETE
(9!%*1) (9!%*2) (9!%*3) (9!%*4)
=.4. The commands as shown above will delete -$$ bac%ups for the file. 5f you 9ust want to delete specific bac%ups, you need to add a :S5;=S parameter.
MIGRAI!" commands HMI%RAT" HMI%RA T" Command /ou /ou use this command to manually migrate a data set. /ou /ou may want to do this a ?
HMIG DSNAME(/) 5 HMIG DSNAME(/) ML2
-nother option is to use the command command below, which which means migrate all files off off volume +5M0# that have not been accessed for ' days.
MIGRATE VOL"ME(PRIM0 VOL"ME(PRIM01 1 MIGRATE()) MIGRATE())
5f you have a problem with M$# filling up, you may need the following command, which migrates all datasets that have been on M$# for 6 days or more to M$6
MIGRATE MIGRATIONLEV MIGRATIONLEVEL1 EL1 DAYS(2) DAYS(2)
/ou /ou can also empty out a primary volume with "HSM by using the 1;=:T parameter. This This means that the datasets are migrated then immediately recalled again. To clear out a volume called +5M0#, set it to "5S=:@ in "SMS, then issue the following command, which will move any files that are not in use elsewhere in the SMS pool. There are much easier ways to move data off a volume of course.
MIGRATE VOL"ME(PRIM0 VOL"ME(PRIM01 1 MIGRATE(0) MIGRATE(0) CONVERT) CONVERT)
HR"CALL Command This command will bring a data set bac% to primary dis%. /ou /ou do not need to recall a file manuallyF "HSM will recall it automatically if you try to use it. However, it can be a pain waiting for a lot of files that are archived to tape, you may want to recall them by command. /ou /ou will also need t use the command if autorecall is having problems. "HSM recall is a file by file operation, you cannot batch up re
HRECALL /
5f "HSM is struggling to find space to recall a large file, you can use either of these two options
HRECALL / DFDSSOPTION VOLCO"NT(ANY) HRECALL / FORCENONSMS "NIT(7!&&?8) VOL"ME('5)
;$1;A=T(-=/ ;$1;A=T(-=/ will ma%e the file go multi!volume, and will use up to '* volumes. /ou /ou can use the ;1:=;=SMS ;1:=;=SMS option to ma%e the recall go to an empty spare volume, but then you have to relocate the file later. /ou /ou can use the H$5ST command to find out how much space the recall needs.
HD"L"T" Command 5f you use the 5S+ line command ?"? or ?":$? to delete migrated files, "HSM will recall the file first, which is a waste of time and resource. 5f you use H":$:T:, then "HSM deletes a migrated data set without recalling the data The 5S+ .8 line command is simply
HDEL /
Ase the +A7: parameter for datasets which have an expiry date set. 5ncidentally, if you are deleting files in batch, then it is best to use 5"1-MS rather than 5:4#8, as then "HSM will delete the file without having to :1-$$ that dataset bac% to dis% first. or example
//STEP01 EXEC PGM#IDCAMS //SYSPRINT DD SYSO"T# //SYSIN DD . DELETE $%&%'&!%*1 DELETE $%&%'&!%*2
bac% to top
HSM System Management Commands /ou /ou would normally use these commands from the TS; command line, prefixed by HS:=", or from the system console using the modify command hsmtas%name,command
QUERY Command /ou /ou use this command to find out what is happening with "HSM. /ou will use these commands so fre
The common commands are •
QUERY ACTIVE - see what processes are running, and the status of the HS co!ponents
•
QUERY "AITI#$ - see how !an% co!!ands are &ueued waiting for resource
•
QUERY AUT'(R'$RESS - )ist out what is happening with HS*s auto!atic functions
•
QUERY USER - )ist the users who are running acti+e or &ueued co!!ands QUERY USERuserid. wi)) )ist out re&uests for a specific user
•
QUERY (R'CESS - &uer% acti+e processes
•
QUERY IA$E - )ist out the na!e of the HS started tas/
•
QUERY AUT'( - )ist out a)) auto!atic processes running at this ti!e
•
QUERY A0ARS - )ist out a)) A0ARS para!eters
•
QUERY AR(''1 - )ist out a)) aggregate reco+er% +o)u!es
•
QUERY (''1 - )ist out a)) the reca)) poo)s
•
QUERY 0AC2U( - )ist out a)) current 3ac/up para!eters This co!!and has so!e optiona) &ua)ifiers, Q 0AC2U(A11. wi)) a)so )ist out the 3ac/up +o)u!es4 5AI1Y.wi)) )ist out dai)% para!eters and dai)% 3ac/up +o)u!es4 +o)u!es4 5AI1Y 5AI1Yda%.. da%.. wi)) )ist out out +o)u!es and and para!eters para!eters for a specific specific da%, da%, whi)e 0AC2U(S(I11. wi)) )ist out spi)) para!eters and spi)) +o)u!es
•
QUERY C5SV - )ist out C5S 3ac/up infor!ation
•
QUERY C5S - )ist out infor!ation a3out the C5S fi)es
•
QUERY 16 - )ist out 16 +o)u!es, inc)uding info a3out +o)u!es that are current)% in use
•
QUERY 5ATASET#AEdatasetna!e. )ist out a)) HS infor!ation for that dataset
•
QUERY S(ACEV'1SER. - )ist out space infor!ation for a specified +o)u!e
•
QUERY STAR - )ist out the HS startup para!eters
•
QUERY RETAI# - )ist out a)) fi)es that are e7c)uded fro! !igration 3% SETI$ co!!ands
•
QUERY CSA1IITS - )ist out the CSA or !e!or% )i!it para!eters for HS
•
QUERY SETSYS - see 3e)ow
CA:/ S:TS/S S:TS/S is useful to see what the "HSM settings are. Some of these are defined in your -11M"xx member in S/S#.+-M$54, S/S#.+-M$54, but they can be overridden by command, command, some system system settings are set by a one!off command, and some ta%e defaults. CA:/ S:TS/S S:TS/S will show you the list of all current system setting.
HOLD Command /ou /ou use this command to pause selected "HSM function. - very useful command in a panic situation is HOLD ALL
which stops all HSM processing. /ou /ou will then probably want to start up selected functions using the release command. HOLD MIGRATION HOLD RECALL(TAPE)
Should both be self explanatory. /ou /ou would want to hold tape recalls if you have a problem with your tape drives, but want recalls f rom M$# to continue as normal.
RELEASE Command 5f something is not wor%ing in "HSM, you could try a CA:/ -1T5: -1T5: command to chec% the status of that "HSM function. 5f it is H:$", then you can release it with the :$:-S: command. ;f course, there may be a reason why it is held, so it is best to chec% this out first. The release command is simply RELEASE 97!<&!
/ou /ou may want to use this in a panic situation as follows HOLD ALL RELEASE RECALL
This holds everything, then releases :1-$$, which minimises user impact.
CANCEL Command /ou /ou use 1-=1:$ to terminate an outstanding "HSM re
/ou /ou identify that the recall is causing problems, and the re
5f a single user has a large number of re
bac% to top
HSM Administration Commands There are some examples of these commands in use, in the started tas% tips page. tips page. "HSM wor%s on volumes, primary volumes hold user accessible data, M$# and M$6 volumes hold migrated data. Three of the volume management commands are
$olume Commands •
ADD$#L & To de'ne volumes to HSM
•
(R""$#L & To move data o) HSM managed volumes
•
D"L$#L & to delete volumes *rom HSM
5 have used these commands to move an HSM M$# volume dynamically. dynamically. /ou /ou cannot use a ""SS 1;+/ of "1;+/ 9ob for this without shutting "HSM down, as "HSM is holding the dis%. /ou could use a product li%e "+-S or T"M, or you can use the procedure below. 1hec% you have enough space to move your volume, if not, clear some space in the M$# pool 5ssue the HSM command
ADDVOL '5 '5 "NIT(33,0) "NIT(33,0) MIGRATION(DRAI MIGRATION(DRAIN) N)
5ssue the HSM command
FREEVOL MVOL('5) AGE(0) TARGETLEVEL(ML1)
The drain process could ta%e an hour or two. 5t is best to move the data to existing M$# volumes, as the recall service is maintained. 5f you move direct to M$6, you loc% out access to the data while your move is running. @hen you get the notify that the freevol command has completed, The M$# volume is now free, so move it your normal way. 5f the volume contains an S"S+, you you can either move it with the dis%, or deleteBredefine it. -dd the volume bac% to HSM, HSM, using the command command
ADDVOL '5 '5 "NIT(33,0) "NIT(33,0) MIGRATION(ML1 MIGRATION(ML1 SDSP NODRAIN) NODRAIN)
Ase the ::;$ command to clear out an M$6 tape. 5f the tape is damaged, then ::;$ will clear out as much as it can and report on all failures.
FREEVOL MVOL('5) TARGETLEVEL(ML2)
A+DIT Command /ou /ou use this command to chec% "HSM control data sets and volumes for problems, and fix the problems. The command to chec% and fix problems with an S"S+ is
HSEND A"DIT MEDCTL(SDSP) VOL"MES(ML1010) : NOFIX ODS(7&87&$% ODS(7&87&$%&%'&) &%'&) HSEND A"DIT MEDCTL(SDSP) VOL"MES(ML1010) : FIX ODS(7&87&$%&%'&)
The command to chec% and fix problems with the 41"S is
HSEND A"DIT BCDS NOFIX ODS(7&87&$%&%'&) HSEND A"DIT BCDS FIX ODS(7&87&$%&%'&)
5f you run the -A"5T with =;5 first, you can chec% your output f ile to ma%e sure that the audit will do what you want. This is not practical if you are auditing a '*0 tape, as it ta%es so long. The command with =;5 will output 51"S commands to your output file. 5t is not a good idea to run the 51"S commands yourself manually, as several of the -A"5T commands will do more than 9ust issue 51"S commands. or instance, -A"5T M:"5-1;=T;$S M:"5-1;=T;$S will also scratch an invalid catalog entry. -A"5T may also create a catalog entry for a data set that is in an S"S+ and has an M1" record but no catalog entry. 5f you 9ust run the 51"S commands manually, you would lose this data.
",PIR"$ command /ou /ou need to run this command to remove expired bac%ups. 5f you do not run the command, the 41"S grows and tapes are never re!used. 5 once went into a site that had not run :+5:4 for over two years, and were struggling to manage a large 41"S. That was one of my
HSEND EXPIREBV EXEC"TE
LIST Command /ou /ou use this command to get information from HSM volumes. - following example is to get information about datasets archived to a tape. This command will produce hundreds of lines of output, so send the output to a dataset, not your terminal.
HSEND LIST TTOC (A010-6) ODS(7&87&$%&%'&) HSEND LIST ML1 TERM
will list out the status of all your M$# volumes.
A+TH Command
/ou /ou use this command the change the access that a user has in "HSM. /ou /ou have three options, AS:, 1;=T;$ or :;):. - AS: can issue all commands except -ATH, /ou must have at least one 1;=T;$ user who can issue -ATH -ATH commands to enable access to others. This can be a problem when testing out disaster recovery procedures, as your authorised user might not be present. @hat you need to do is add a line to your -11M"xx member member as shown below, with ?userid? set to an on!site user.
A"TH 7'5$ 7'5$ DBA(CONTROL) DBA(CONTROL)
/ou /ou then need to ?bounce? "HSM. To find out who is authorised to use HSM commands, use
HSEND LIST "SER
(I,CDS Command /ou /ou use this command to display or alter data within the three 1"S files. 54M seem to have withdrawn the documentation for this command. The -A"5T command will build 51"S commands as described above, so when you use the -A"5T command you can see 51"S in use. The example below is a fix to reset the S"S+ en
TSO HSEND FIXCDS V '5
@here volser is the M$# volume that contains the S"S+ file. 1hec% field x?'*? in the display output. 5f bi t ' at x?'*? is on then issue the following command2
F HSM;FIXCDS V '5 PATCH(X, BITS(0))
There are some other examples of the use of 51"S in the ?HSM Tape Tape and "ataset tips? section
Statistics %at-ering Commands The :+;T command command will tell you things li%e how many files have been migrated, bac%ed up, recalled and restored. The syntax to get the current stats is
HSEND REPORT DAILY F"NCTION
5f you leave function li%e that, you will get stats on all the HSM functions, or you can as% for a specific function with A=1T5;=(4-1)A+ or ":$:T:, M57-T5;=, :1-$$ or :1;:. /ou /ou can also get data for several days with the ;M and T;"-T: T;"-T: parameters, how much you will get will depend on how often you purge this data from HSM
HSEND LIST DAILY F"NCTION(RECALL) FROMDATE(0-/0/01) TODATE(0-/0/1)
/ou /ou can also report on volume activity with the :+;T ;$AM:S ;$AM:S command. 5f you specify a particular ;$S: you will get a detailed dataset report for that volume. 5f you do not, you get a summary report for every volume that HSM has. +ipe this one to a file, it will contain a lot of data.
HSEND REPORT VOL"MES(8&!%'5) ODS(9!%*)
bac% to top
