Hey Bill,
I found that my problem causing the RC 127 was I had put the script
in /etc/tsm/amnthfs.sh and had a preschedulecmd that was looking for
/etc/amnthfs.sh . I had the path wrong. It seems to be interesting
working with this. We have a 3 lpar environment so I have to go through the
process. I wrote a job that I scheduled to run everyday about an hour
before the backups. It has 3 steps. Step1 does an IDCAMS DCOLLECT of the
3 disk volumes that have user HFSs. Step2 is a SAS program that parses the
output of the DCOLLECT for all the user HFS's and it writes out a script
that will do a CD /U/XXXX (where XXXX is the user) for each user HFS,
this gets them mounted. Step 3 just copies the script to the
/etc/tsm/amnthfs.sh file.
Matt
-----Original Message-----
From: Bill Boyer [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 9:26 AM
To: [EMAIL PROTECTED]
Subject: Re: PRESCHEDULECMD on OS390 unix, rc 127
Unless you're in a Sysplex environment where these users may log on to
different systems, I would set my automount timeout to never de-mount the
automounted user HFS and then just let TSM backup all mounted HFS's. If a
user never logged on, there's no sense in backing up his HFS as it probably
never changed. This is the DURATION parameter in the /etc/u.map.
If they're logging on to different systems in the Sysplex, then maybe you'll
have to live with backing up the HFS files as a whole with DFDSS.
Maybe the error you're running into is security, or the filemasking in the
/etc/u.map file. The DSNAME of the HFS is determined by incorporating the
userid of who is currently logged on.
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
MC Matt Cooper (2838)
Sent: Friday, February 01, 2002 7:37 AM
To: [EMAIL PROTECTED]
Subject: PRESCHEDULECMD on OS390 unix, rc 127
Hello all,
I am trying to get a PRESCHEDULECMD script that will automount all
the users HFSs for backup. I know there is a command for automount but I
have to update the list of users automounted daily. We are just getting
into this area and it is growing. Anyway, I execut the script
successfully from the OS390 Unix environment but when I added to the backup
as a PRESCHEDULECMD I got a RC 127. I can not find the interpretation of
the message. Anyone know what it is or where I should be looking it up?
>From the DSMSCHED.LOG
.......
02/01/2002 00:00:08 Server Window Start: 00:00:01 on 02/01/2002
02/01/2002 00:00:08
------------------------------------------------------------
02/01/2002 00:00:08
Executing scheduled command now.
02/01/2002 00:00:08
Executing Operating System command or script:
/etc/amnthfs.sh
02/01/2002 00:00:09 Finished command. Return code is:
127
02/01/2002 00:00:09 --- SCHEDULEREC OBJECT BEGIN MVS-DAILY 02/01/2002
00:00:01
There was nothering in the DSMERROR.LOG
The DSM.SYS looks like
********************************* Top of Data *****
SERVERNAME MVS1CMF
COMMmethod TCPip
NODENAME AG04
TCPPort 1500
TCPServeraddress 192.168.100.252
SCHEDLOGNAME /var/tsm/dsmsched.log
SChEDLOGRETENTION 10
ERRORLOGNAME /var/tsm/dsmerror.log
ERRORLOGRETENTION 10
PASSWORDACCESS GENERATE
SCHEDMODE PROMPTED
INCLEXCL /etc/tsm/inclexcl.txt
TCPWindowsize 64
RETRYPERIOD 15
MAXCMDRETRIES 10
LARGECOMMBUFFERS YES
COMMRESTARTINTERVAL 60
COMMRESTARTDURATION 300
preschedulecmd '/etc/amnthfs.sh'
The script looks like..
BROWSE -- /etc/tsm/amnthfs.sh -
#!/bin/sh
cd /u/MKC$
cd /u/HPZ$
cd /u/CSB$
cd /u/RDH$
cd /u/JEJ$
cd /u/CMR$
cd /u/CD1$
