Re: z/OS Unix System Services Backups

2013-05-24 Thread R.S.

W dniu 2013-05-23 18:57, Mike Schwab pisze:

z/TSM has been obsolete, is going out of support, and may or may not
work on z/OS 2.1.
We backup the root system on the IPL volumes with ADRDSSU.
The system HFS/zFS are backed up with ADRDSSU Logical, and is OK since
they don't have running applications.

Application HFS/zFS are backed up with z/TSM and attempts to use
ADRDSSU resulted in hangs due to the quiescent request.

z/TSM is being used, has been obsolete, is going out of support, and
may not work on z/OS 2.1.

Does anyone have a comparison of the backup and restore alternatives
that work while the application is running?
TSM on AIX,
FDR Upstream Unix,
CA Disk Backup and Restore for Unix System Services,
Others?



Harbor Backup aka Betasystems aka Tantia
pax

BTW: IMHO the real problem is ADRDSSU operates at filesystem level, so 
lacks granularity at file/directory level. You don't want to restore 
multi-GB filesystem just to recover single file. Not to mention 
cumbersome method to avoid overwriting the rest of the filesystem with 
older version.


--
Radoslaw Skorupka
Lodz, Poland






--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. 


BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax 
+48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych.



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


z/OS Unix System Services Backups

2013-05-23 Thread Mike Schwab
z/TSM has been obsolete, is going out of support, and may or may not
work on z/OS 2.1.
We backup the root system on the IPL volumes with ADRDSSU.
The system HFS/zFS are backed up with ADRDSSU Logical, and is OK since
they don't have running applications.

Application HFS/zFS are backed up with z/TSM and attempts to use
ADRDSSU resulted in hangs due to the quiescent request.

z/TSM is being used, has been obsolete, is going out of support, and
may not work on z/OS 2.1.

Does anyone have a comparison of the backup and restore alternatives
that work while the application is running?
TSM on AIX,
FDR Upstream Unix,
CA Disk Backup and Restore for Unix System Services,
Others?

-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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


Re: z/OS Unix System Services Backups

2013-05-23 Thread Ed Jaffe

On 5/23/2013 9:57 AM, Mike Schwab wrote:

z/TSM is being used, has been obsolete, is going out of support, and
may not work on z/OS 2.1.

Does anyone have a comparison of the backup and restore alternatives
that work while the application is running?
TSM on AIX,
FDR Upstream Unix,
CA Disk Backup and Restore for Unix System Services,
Others?


After IBM stabilized TSM for z/OS at the 5.5 level, we deployed a 
hipersocket-connected RHEL Linux for z image where we currently run TSM 
6.2. What's nice is that we can still use TSM clients on z/OS for both 
backup and administrative purposes and TSM still uses host-attached tape 
drives.


--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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


Re: z/OS Unix System Services Backups

2013-05-23 Thread van der Grijn, Bart (B)
We had a similar dilemma (although never used TSM). The ADRDSSU backups were 
disruptive to our applications. 
We've considered using Flashcopy for the backups, but as far as I can tell we 
can't do a logical backup that way, and the reality is that we typically need 1 
or more files from a backup, not the whole filesystem. 

At the moment we use a pax script to back up to sequential datasets which are 
then archived by HSM.

It works, but it's not pretty, and I hope your question results in some better 
alternatives.

Bart

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Schwab
Sent: Thursday, May 23, 2013 12:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: z/OS Unix System Services Backups

z/TSM has been obsolete, is going out of support, and may or may not
work on z/OS 2.1.
We backup the root system on the IPL volumes with ADRDSSU.
The system HFS/zFS are backed up with ADRDSSU Logical, and is OK since
they don't have running applications.

Application HFS/zFS are backed up with z/TSM and attempts to use
ADRDSSU resulted in hangs due to the quiescent request.

z/TSM is being used, has been obsolete, is going out of support, and
may not work on z/OS 2.1.

Does anyone have a comparison of the backup and restore alternatives
that work while the application is running?
TSM on AIX,
FDR Upstream Unix,
CA Disk Backup and Restore for Unix System Services,
Others?

-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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


Re: z/OS Unix System Services Backups

2013-05-23 Thread Mark Post
 On 5/23/2013 at 01:17 PM, Ed Jaffe edja...@phoenixsoftware.com wrote: 

 After IBM stabilized TSM for z/OS at the 5.5 level, we deployed a 
 hipersocket-connected RHEL Linux for z image where we currently run TSM 
 6.2. What's nice is that we can still use TSM clients on z/OS for both 
 backup and administrative purposes and TSM still uses host-attached tape 
 drives.

How did you pull off using host-attached tapes when IBM says TSM on Linux for 
System z doesn't support that?


Mark Post

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


Re: z/OS Unix System Services Backups

2013-05-23 Thread Mike Schwab
On Thu, May 23, 2013 at 12:20 PM, Mark Jacobs mark.jac...@custserv.com wrote:

 We backup all of our zFS file systems with ADRDSSU logical backups and have
 never had any problems. Can you post a sample DFDSS job step (with control
 cards) for people to look at?

 --
 Mark Jacobs

-SPRX054  STEP02  04   4905   115K   .00   .002.1 40607
IEF233A M A0D6,PRIVAT,SL,IDCCLWX3,STEP02,,MEDIA4
TMS001  IEF233A M A0D6,PRIVAT,SL,IDCCLWX3,STEP02,,MEDIA4,IDCVVLT.WOMVSX.G0063V00
IECTMS9 A0D6,K35560,IDCCLWX3,TAPE1   ,CATLG/006 ,1,T.WOMVSX.G0063V00
IEC705I TAPE ON A0D6,K35560,SL,COMP,IDCCLWX3,STEP02.SOMVSX,MEDIA4
IEC502E K A0D6,K35560,SL,IDCCLWX3,STEP02
TMS014  IEC502E K A0D6,K35560,SL,IDCCLWX3,STEP02
IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
TMS001  IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
IECTMS9 A0D6,Q07554,IDCCLWX3,TAPE1   ,CATLG/006 ,1,T.WOMVSX.G0063V00
IEC705I TAPE ON A0D6,Q07554,SL,COMP,IDCCLWX3,STEP02.SOMVSX,MEDIA4
IEC502E K A0D6,Q07554,SL,IDCCLWX3,STEP02
TMS014  IEC502E K A0D6,Q07554,SL,IDCCLWX3,STEP02
IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
TMS001  IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
IECTMS9 A0D6,Q08449,IDCCLWX3,TAPE1   ,CATLG/006 ,1,T.WOMVSX.G0063V00
IEC705I TAPE ON A0D6,Q08449,SL,COMP,IDCCLWX3,STEP02.SOMVSX,MEDIA4
IEC502E K A0D6,Q08449,SL,IDCCLWX3,STEP02
TMS014  IEC502E K A0D6,Q08449,SL,IDCCLWX3,STEP02
IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
TMS001  IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
IECTMS9 A0D6,M11531,IDCCLWX3,TAPE1   ,CATLG/006 ,1,T.WOMVSX.G0063V00
IEC705I TAPE ON A0D6,M11531,SL,COMP,IDCCLWX3,STEP02.SOMVSX,MEDIA4
IEC502E K A0D6,M11531,SL,IDCCLWX3,STEP02
TMS014  IEC502E K A0D6,M11531,SL,IDCCLWX3,STEP02
IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
TMS001  IEC501A M A0D6,PRIVAT,SL,COMP,IDCCLWX3,STEP02.SOMVSX,,MEDIA4
IECTMS9 A0D6,J86929,IDCCLWX3,TAPE1   ,CATLG/006 ,1,T.WOMVSX.G0063V00
IEC705I TAPE ON A0D6,J86929,SL,COMP,IDCCLWX3,STEP02.SOMVSX,MEDIA4
IEC205I TAPE1,IDCCLWX3,STEP02,FILESEQ=1, COMPLETE VOLUME LIST,  209
VOLS=K35560,Q07554,Q08449,M11531,J86929,TOTALBLOCKS=707025
IEF234E K A0D6,J86929,PVT,IDCCLWX3,STEP02
-SOMVSX   STEP02  00  3957K 14537K   .90   .23  265.8   7090889

//*
//* IDCOMVS  DS FOR 'X' SYSTEM
//**SOMVSX*
//SOMVSX   EXEC VBACKUP,VOL1=OMVSX,PARM='ABEND=960'
XXVBACKUP PROC EXPDT1=90006,UNIT1=VTAPE,TYPE1=W,MEM1=DUMPPHY1,
XX*VBACKUP PROC RETPD1=27,UNIT1=CART2,TYPE1=W,MEM1=DUMPPHY1,
XXPREFIX=IDCVVLT,GEN='(+1)',DISP1='NEW,CATLG,DELETE'
XX IDCRMGS.PROCLIB(VBACKUP)
XXSTEP02  EXEC PGM=ADRDSSU,COND=EVEN,PARM='ABEND=415'
XXSYSPRINT DD  SYSOUT=*
XXSYSMDUMP DD  SYSOUT=*
XXTAPE1DD  DSN=PREFIX..TYPE1VOL1GEN,LABEL=EXPDT=EXPDT1,
XX*TAPE1DD  DSN=PREFIX..TYPE1VOL1(GEN),RETPD=RETPD1,
XX DCB=(IDCRMGS.MODLDSCB),DISP=(DISP1),
XX UNIT=UNIT1,VOL=(,,,10)
IEFC653I SUBSTITUTION JCL - DSN=IDCVVLT.WOMVSX(+1),LABEL=EXPDT=90006,
DCB=(IDCRMGS.MODLDSCB),DISP=(NEW,CATLG,DELETE),UNIT=VTAPE,VOL=(,,,10)
//SYSIN DD  *
X/SYSINDD  DSN=IDCRMGS.PARMLIB(MEM1),DISP=SHR
//*
PAGE 0001 5695-DF175  DFSMSDSS V1R13.0 DATA SET SERVICES 2013.138 03:13
ADR004I (SCH)-PRIME(01), USER ABEND 0001 WILL BE ISSUED ON OCCURRENCE
0001 OF MESSAGE ADR960
 DUMP ODD(TAPE1) TOL(ENQF) -
 DS(INCL(*OMVS.SYSX.**,*OMVSX.SYSX.**) -
EXCL(IDCOMVSX.SYSX.TMP.*,IDCOMVSX.SYSX.TMPX.*))
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP '
ADR109I (R/I)-RI01 (01), 2013.138 03:13:39 INITIAL SCAN OF USER
CONTROL STATEMENTS COMPLETED
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
ADR006I (001)-STEND(01), 2013.138 03:13:39 EXECUTION BEGINS
ADR801I (001)-DTDSC(01), 2013.138 07:39:28 DATA SET FILTERING IS
COMPLETE. 57 OF 57 DATA SETS WERE SELECTED: 0 FAILED SERIALIZATION
 AND 0 FAILED FOR OTHER REASONS
ADR454I (001)-DTDSC(01), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED
  CLUSTER NAME   BESOMVS.SYSX.BESPROD.WEBLOGS.ZFS
  CATALOG NAME   ICFCAT.BESSHR
  COMPONENT NAME BESOMVS.SYSX.BESPROD.WEBLOGS.ZFS.DATA
  CLUSTER NAME   BESOMVS.SYSX.BESPROD.ZFS
  CATALOG NAME   ICFCAT.BESSHR
...
  CATALOG NAME   ICFCAT.MHDSHR
  COMPONENT NAME MHDOMVS.SYSX.MHD5662.ZFSTRY.DATA
ADR006I (001)-STEND(02), 2013.138 07:39:28 EXECUTION ENDS
ADR013I (001)-CLTSK(01), 2013.138 07:39:28 TASK COMPLETED WITH RETURN CODE 
ADR012I (SCH)-DSSU (01), 2013.138 07:39:28 DFSMSDSS PROCESSING
COMPLETE. HIGHEST RETURN CODE IS 

-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from 

Re: z/OS Unix System Services Backups

2013-05-23 Thread Ed Jaffe

On 5/23/2013 10:43 AM, Mark Post wrote:

After IBM stabilized TSM for z/OS at the 5.5 level, we deployed a
hipersocket-connected RHEL Linux for z image where we currently run TSM
6.2. What's nice is that we can still use TSM clients on z/OS for both
backup and administrative purposes and TSM still uses host-attached tape
drives.

How did you pull off using host-attached tapes when IBM says TSM on Linux for 
System z doesn't support that?


Sorry. That was a misleading statement. They are the identical host tape 
drives, but we use the FCP attachment for Linux on z instead of the 
traditional FICON attachment that we use for z/OS.


--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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


Re: z/OS Unix System Services Backups

2013-05-23 Thread Ed Jaffe

On 5/23/2013 10:46 AM, Mark Jacobs wrote:
IBM has a stripped down version of TSM that executes on zOS that does 
the actual tape I/O. TSM on another platform connects to the TSM 
running on zOS.


Order number?

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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


Re: z/OS Unix System Services Backups

2013-05-23 Thread Mark Jacobs
[5698-Z01]  TSM for z/OS or
[5698-Z02]  TSM EE for z/OS 

Mark Jacobs

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Ed 
Jaffe [edja...@phoenixsoftware.com]
Sent: Thursday, May 23, 2013 6:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS Unix System Services Backups

On 5/23/2013 10:46 AM, Mark Jacobs wrote:
 IBM has a stripped down version of TSM that executes on zOS that does
 the actual tape I/O. TSM on another platform connects to the TSM
 running on zOS.

Order number?

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

--
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