Archives of the TeradataForum

Message Posted: Mon, 20 Mar 2006 @ 10:55:46 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hi Cesar,

If you want to store the job output to a file you could try something like this.

For re-runability you would need to drop the output before you re-run it.

Step one drops output file (if it's there or not): DW.MLOAD.SYSPRINT

Multiload step loads a file called : DW.LoadFile
using a script called : DW.MLOAD.LOADJOB

The output of the job will go to a file called DW.MLOAD.SYSPRINT you will need to specify what type of tape/disk Unit to write depending on your set-up (Test or Production)

     //STEP01   EXEC PGM=IEFBR14,COND=(0,NE)
     //DD1       DD DSN=DW.MLOAD.SYSPRINT,
     //             DISP=(MOD,DELETE,DELETE),
     //             UNIT=SYSDA,
     //             SPACE=(TRK,0)
     //*
     //MULTILOD EXEC PGM=MLOAD,COND=(0,NE)
     //STEPLIB   DD DSN=DW.TDP.APPLOAD,DISP=SHR


     //              DD DSN=DW.TDP.TRLOAD,DISP=SHR


     //SYSOUT    DD SYSOUT=*
     //SYSPRINT  DD DSN=DW.MLOAD.SYSPRINT,
     //             DISP=(,CATLG,CATLG),
     //             UNIT=xxxx
     //             DCB=(RECFM=FB,LRECL=259,BLKSIZE=0,DSORG=PS),
     //             SPACE=(TRK,(1,1),RLSE)
     //SYSTERM   DD SYSOUT=*
     //MLOADIN   DD DSN=DW.LoadFile,
     //             DISP=SHR
     //SYSIN     DD DSN=Logon.File,
     //             DISP=SHR
     //          DD DSN=DW.MLOAD.LOADJOB,
     //             DISP=SHR

Best of luck,

Fachtna O'Donovan
Data Warehouse Software Engineer
AIB Bank
Ireland

	<Prev	Next>		<<First	<Prev	Next>	Last>>