Answers:
1) OS/390 2.10

2) output from Q SETSYS:

QUERY SETSYS COMMAND STARTING ON HOST=1
BUDENSITY=*, BUUNIT=TAPE90, BU RECYCLE 609
(CONT.) PERCENTAGE=033%, MOUNT WAIT TIME=010 MINUTE(S),
(CONT.) TAPESPANSIZE(0100)
SELECTVOLUME=SCRATCH, 610
(CONT.) TAPEDELETION=SCRATCHTAPE, PARTIALTAPE=MARKFULL,
(CONT.) DISASTERMODE=NO
INPUT TAPE ALLOCATION=NOWAIT, OUTPUT TAPE 611
(CONT.) ALLOCATION=NOWAIT, RECYCLE TAPE ALLOCATION=NOWAIT,
(CONT.) TAPEFORMAT=SINGLEFILE
TAPE INPUT PROMPT FOR BACKUPTAPES=NO
TAPE INPUT PROMPT FOR DUMPTAPES=NO
TAPE INPUT PROMPT FOR MIGRATIONTAPES=NO
TAPE OUTPUT PROMPT FOR TAPECOPY=NO, DUPLEX 615
(CONT.) BACKUP TAPES=NO, DUPLEX MIGRATION TAPES=NO
TAPEMIGRATION=ML2TAPE(TAPE(TAPE90)), 616
(CONT.) MIGDENSITY=*, MIGUNIT=TAPE90, ML2 RECYCLE
(CONT.) PERCENTAGE=033%, TAPEMAXRECALLTASKS=01, ML2 PARTIALS
(CONT.) NOT ASSOCIATED GOAL=010, RECONNECT(NONE)
TAPESECURITY=EXPIRATION, DEFERMOUNT
RECYCLEOUTPUT BACKUP=**NONE**, 618
(CONT.) MIGRATION=**NONE**
MAXRECYCLETASKS=01, RECYCLE INPUT 619
(CONT.) DEALLOCATION FREQUENCY BACKUP=000 MIGRATION=000
MONITOR STARTUP NOSPACE NOVOLUME, MCDS(080), 620
(CONT.) BCDS(080), OCDS(080), JOURNAL(080)
JOURNAL=RECOVERY, LOG=YES, TRACE=NO, 621
(CONT.) SMFID=0240, DEBUG=NO, EMERG=NO, JES=2, SYS1DUMP=YES,
(CONT.) RACFIND=NO, ERASEONSCRATCH=NO, PDA=ON
DAYS=380, ML1DAYS=003, 622
(CONT.) PRIMARYSPMGMTSTART=(0030 0430),
(CONT.) MAXMIGRATIONTASKS=0002, INTERVALMIGRATION=NO,
(CONT.) MIGRATIONCLEANUPDAYS(0014 0007 0003), SDSP=NONE,
(CONT.) MIGRATION PREFIX=DFHSM, SCRATCH EXPIRED DATA SETS=YES,
(CONT.)  SECONDARYSPMGMTSTART=(0015 0330)
PRIMARY SPACE MGMT CYCLE LENGTH=07 DAYS, 623
(CONT.) CYCLE=NNNYNNN, TODAY IS DAY=07, CYCLE START
(CONT.) DATE=01/01/26, SECONDARY SPACE MGMT CYCLE LENGTH=07
(CONT.) DAYS, CYCLE=NNNYNNN, TODAY IS DAY=07, CYCLE START
(CONT.) DATE=01/01/26
MAXINTERVALTASKS=0002
ACCEPTPSCBUSERID=NO
MAXRECALLTASKS=02, RECALL=PRIVATEVOLUME(LIKE), 626
(CONT.)  MAXEXTENTS=10, CONVERSION=NO, VOLCOUNT=*NONE*,
(CONT.) TAPERECALLLIMITS(TASK=00015, TAPE=00020)
SCRATCHFREQ=0007, SYSOUT(CLASS=T, COPIES=01, 627
(CONT.) SPECIAL FORMS=NONE), SWAP=NO, PERMISSION=NO, EXITS=TV,
(CONT.)  UNLOAD=NO, DATASETSERIALIZATION=DFHSM
TAPEUTILIZATION PERCENT=0097, LIBRARYMIGRATION
TAPEUTILIZATION PERCENT=0097, LIBRARYBACKUP
TAPEUTILIZATION PERCENT=0097, UNIT=3480 630
(CONT.) CAPACITYMODE=**NONE**
TAPEUTILIZATION PERCENT=0097, UNIT=3480X 631
(CONT.) CAPACITYMODE=**NONE**
TAPEUTILIZATION PERCENT=0097, UNIT=3490 632
(CONT.) CAPACITYMODE=**NONE**
TAPEUTILIZATION PERCENT=0097, UNIT=3590-1 633
(CONT.) CAPACITYMODE=**NONE**
TAPEUTILIZATION PERCENT=0097, UNIT=TAPE90 634
(CONT.) CAPACITYMODE=**NONE**
MAXDUMPTASKS=01, ADSTART=(1500 1730 2230), 635
(CONT.) DUMPIO=(4,4), VOLUMEDUMP=(NOCC)
BACKUP=YES(TAPE(TAPE90)), SPILL=NO, 636
(CONT.) MAXDSRECOVERTASKS=01
MAXBACKUPTASKS=01, ABSTART= (1530 2100 2145), 637
(CONT.) VERSIONS=002, FREQUENCY=002, SKIPABPRIMARY=NO, BACKUP
(CONT.) PREFIX=DFHSM, INCREMENTALBACKUP=CHANGEDONLY,
(CONT.) PROFILEBACKUP=YES, INUSE=(RETRY=YES, DELAY=002,
(CONT.) SERIALIZATION=PREFERRED)
DATA SET DASD BACKUP TASKS=02 DATA SET TAPE 638
(CONT.) BACKUP TASKS=02, DEMOUNTDELAY MINUTES=0060,
(CONT.) MAXIDLETASKS=00, DATA SET BACKUP MAXIMUM DASD
(CONT.) SIZE=003000, DATA SET BACKUP STANDARD DASD
(CONT.) SIZE=000250, SWITCHTAPES TIME=0000,
(CONT.) PARTIALTAPE=MARKFULL
USER UNIT NAMES=TAPE90
CDSVERSIONBACKUP, 640
(CONT.) MCDSBACKUPDSN=DFHSM.MCDS.BACKUP,
(CONT.) BCDSBACKUPDSN=DFHSM.BCDS.BACKUP,
(CONT.) OCDSBACKUPDSN=DFHSM.OCDS.BACKUP,
(CONT.) JRNLBACKUPDSN=DFHSM.JRNL.BACKUP
BACKUPCOPIES=0004, BACKUPDEVICECATEGORY=DASD, 641
(CONT.) LATESTFINALQUALIFIER=D0004293, DATAMOVER=DSS
CSALIMITS=YES, CSA CURRENTLY USED=0 BYTES, 642
(CONT.) MWE=4, MAXIMUM=100K BYTES, ACTIVE=90%, INACTIVE=30%
COMPACTION OPTIONS ARE: TAPEMIGRATION=YES, 643
(CONT.) DASDMIGRATION=YES, TAPEBACKUP=YES, DASDBACKUP=YES,
(CONT.) TAPEHARDWARECOMPACT=YES
COMPACT PERCENT IS 30%
SOURCENAMES: ASM      COBOL    FORT     PLI 645
(CONT.)    SOURCE
SOURCENAMES: SRC      SRCLIB   SRCE     CNTL 646
(CONT.)    JCL
OBJECTNAMES: OBJ      OBJECT   LOAD 647
(CONT.) LOADLIB  LOADMODS
OBJECTNAMES: LINKLIB
OPTIMUMDASDBLOCKING=YES, LOGGING 649
(CONT.) LEVEL=EXCEPTIONONLY, LOG TYPE=SYSOUT T
AGGREGATE BACKUP/RECOVERY PROCNAME = DFHSMABR
AGGREGATE BACKUP/RECOVERY MAXADDRESSSPACE = 01
AGGREGATE BACKUP/RECOVERY UNIT NAME = 3590-1
AGGREGATE BACKUP/RECOVERY ACTIVITY LOG 653
(CONT.) MESSAGE LEVEL IS FULL
AGGREGATE RECOVERY ML2 TAPE UNIT NAME = 3590-1
NUMBER OF ABARS I/O BUFFERS = 01
ABARS ACTIVITY LOG OUTPUT TYPE = SYSOUT(T)
AGGREGATE RECOVERY UNIT NAME = 3590-1
AGGREGATE BACKUP OPTIMIZE = 3
AGGREGATE RECOVERY TGTGDS = SOURCE
AGGREGATE RECOVERY ABARSVOLCOUNT = *NONE*
AGGREGATE RECOVERY PERCENTUTILIZED = 080
AGGREGATE BACKUP/RECOVERY ABARSDELETEACTIVITY 662
(CONT.) = NO
AGGREGATE BACKUP/RECOVERY ABARSTAPES = STACK
AGGREGATE BACKUP ABARSKIP = NOPPRC, NOXRC
PLEXNAME=ARCPLEX0,PROMOTE PRIMARYHOST=NO, 665
(CONT.) PROMOTE SSM=NO
QUERY SETSYS COMMAND COMPLETED ON HOST=1

3) from log
*TMS009 IEC501A M 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET
*IEC501A M 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET
*0037 ARC0310A CAN TAPE 015010 BE MOUNTED? REPLY Y OR N
 R 37,N
 IEE600I REPLY TO 0037 IS;N
 IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DFSMSHSM, ASID=0027.
 IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DFSMSHSM, ASID=0027.
 IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=DFSMSHSM, ASID=0027.
 ARC0421I BACKUP VOLUME 015010 IS NOW MARKED FULL
 TMS014  IEF234E K 0C01,015010,PVT,DFSMSHSM,DFSMSHSM
 IEF234E K 0C01,015010,PVT,DFSMSHSM,DFSMSHSM
*TMS009 IEC501A M 0C02,015128,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET
*IEC501A M 0C02,015128,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET


Tony Thigpen

Lizette Koehler wrote on 11/22/2016 10:10 PM:
So some basic questions
   1)  What version of z/OS?
   2)  If you do a F dfhsmtaskname,Q SETSYS   does it show the same info as the 
ARCCMDxx member?
   3)  What is the specific messages  you are seeing during autobackup?


Lizette


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Tony Thigpen
Sent: Tuesday, November 22, 2016 4:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: HSM question

HSM is not my ballgame, but I am tasked with figuring out this puzzle, so bear
with me. As for background, the shop attempts to run lights-out 24/7.

Once a week, HSM performs an AUTOBACKUP. Until about 3 months ago, if nobody
was at the shop, HSM would ask for an exiting tape, wait 10 minutes, and if no
tape was mounted, it would ask "Can tape be mounted?". If our remote operator
replied 'N', then HSM would us a scratch tape. About once ever month or so, we
would run a recycle job to combine all the tapes.

About 3 months ago, we had some internal discussions about 'fixing' this so
that it would just use scratch tapes without asking for an existing tape. The
next thing we knew, the weekly tapes would automatically use a scratch tape.
This was good. I assumed that one of the other guys had changed something.

Then came the time change and the resulting IPL. Now everything is different.
It seems to work the way it did prior to 3 months ago, except for one problem.
When the operator replies that the tape can not be mounted, instead of HSM
using a scratch tape, it now asks for another HSM tape. After about 4 hours of
this last week, I got in my car and went down an mounted the tape. (I am the
only one that lives in the same town as the processor.)

Discussions with all the 3 others involved in the discussion 3 months ago came
back with "I did not change anything 3 months ago."

But, the other 2 guys that know HSM also say "We are busy. If you want it
different, figure it out and change it."

Key items I see in the config file are:
SETSYS
    PARTIALTAPE(
     BACKUP(MARKFULL) -
     MIGRATION(MARKFULL))
SETSYS
    SELECTVOLUME(
    BACKUP(SCRATCH)
    MIGRATION(SCRATCH) -
    DUMP(SCRATCH))
SETSYS
    RECYCLEPERCENT(33)
    MAXRECYCLETASKS(1)
SETSYS
    TAPEUTILIZATION(
     UNITTYPE(3590-1) PERCENTFULL(97))
SETSYS
    TAPESPANSIZE(100)

(And the output of HSEND QUERY SETSYS is the same.)

The last update date stamp on the config files was 15/12/22.

So, I have come to the conclusion that somebody issued a command to HSM but
did not update the config file so it would be handled at the next IPL.

Looking for any input.

--
Tony Thigpen

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to