The FTP command used to send file from Optim(setup in SQL server VM) to z/OS is,



open -s:%0

IBMXXXX.XX.XXXXXX.NET

????????

ascii

quote site blksize=3120 recfm=fb lrecl=80 conddisp=delete

binary

quote site blocks PRImary=483640 SECondary=10

put "E:\Data\XXXXX\XXXXX003_DPEXT.000" "''XXXXXXX.XXXXX003.X000''"

binary

quote site blocks PRImary=9 SECondary=10

put "E:\Data\XXXXX\XXXXX003_DPEXT.500" "''XXXXXXX.XXXXX003.S500''"

ascii

quote site blksize=800 recfm=fb lrecl=80 conddisp=delete

quote site blocks PRImary=3 SECondary=10

put "E:\Data\XXXXX\XXXXX003_DPEXT.JCL" "''XXXXXXX.XXXXX003.JCL''"

bye



I don't think the FTP process will compress the file while sending to z/OS.







I'm using following JCL to execute RECEIVE command.



//TSORECV EXEC PGM=IKJEFT01

//COPYIN DD DSN=myuserid.XXXXX003.X000,DISP=SHR

//SYSTSPRT DD SYSOUT=*

//SYSTERM DD SYSOUT=*

//SYSIN DD DUMMY

//SYSTSIN DD *

PROFILE PREFIX(DBWORK)

RECEIVE -

INFILE(COPYIN)

DSN(XXXXX003.I000) SPACE(200,200) CYLINDERS BLKSIZE(132) NEW

/*







On Wed, 11 Nov 2015 06:18:24 +0530 Lizette Koehler  wrote

>Sorry, I have not followed this thread completely, so this may already have 
>been answered.







First your statement:



The input file attributes are: DSORG=SEQUENTIAL, RECFM=VB, BLKSIZE=132, 
LRECL=128, File 

size=X'001BD216'K bytes



This is an unblocked file. That means there is one record for every block. This 
is not very efficient.







Next, you need to show the TSO XMIT command and part of the output. I have a 
provided a sample below.



Then you need to go to 3.4 and show us the attributes of the output file, I 
have provided a sample 

below.















Did you use TSO XMIT or TSO TRANSMIT to create your FILE? Or did you use 
another process?







Please show the messages on how the file was created.







Typically a TSO XMIT Dataset will have a LRECL(80) BLKSIZE(3120). Or you may 
have used TRSMAIN, which 

has a different set of LRECL and BLKSIZE.







It is important to know how you created the file and what the attributes were 
of the file that was 

created.







For example:







DSLIST - Data Sets Matching MYTSOID.PDS.CNTL 



Command ===>                 



                       



Command - Enter "/" to select action     



---------------------------------------------



xmit indsn(/) outdsn(test.xmi)        



XMIT lpar.mytsoid dsn(/) outdsn(test.xmi)  



                     IEBCOPY MESSAGES AND CONTROL STATEMENTS               PAGE 
  1    



 IEB1135I IEBCOPY FMID HDZ2210 SERVICE LEVEL UA74516 DATED 20140814 DFSMS 
02.01.00 z/OS  02.01.00 

HBB7790 CPU 2817    



 IEB1035I mytsoid TSOPROC0 TSOPROC0 17:22:29 TUE 10 NOV 2015 
PARM='WORK=4M,SIZE=1M'                      



 COPY OUTDD=SYS00039,INDD=((SYS00035,R))                                        
    



 IEB1013I COPYING FROM PDS  INDD=SYS00035 VOL=TSOT15 DSN=mytsoid.PDS.CNTL       
                    



 IEB1014I      TO PDSU OUTDD=SYS00039 VOL=    
DSN=SYS15314.T172229.RA000.mytsoid.R0124442                



 IEB167I FOLLOWING MEMBER(S) UNLOADED FROM INPUT DATA SET REFERENCED BY 
SYS00035                        



                                       



General Data              Current Allocation           



 Management class . . :M18       Allocated blocks . :9,045      



 Storage class . . . :SCNORMAL    Allocated extents . :1       



 Volume serial . . . :TSOT14                        



 Device type . . . . :3390                         



 Data class . . . . . :DEF001                        



 Organization . . . :PS       Current Utilization          



 Record format . . . :FB       Used blocks . . . . :9,045      



 Record length . . . :80       Used extents . . . :1        



 Block size . . . . :3120                         



 1st extent blocks . :9045                         



 Secondary blocks . :4140      Dates                 



 Data set name type :         Creation date . . . :2015/11/10   



                    Referenced date . . :2015/11/10   



                    Expiration date . . :***None***   



 SMS Compressible . :NO                          



                                       







I can then download to my PC and FTP to another site. To download to the PC you 
would use BIN







So the difference might be due to 



1) The LRECL and BLKSIZE do not match on both sides. For my example the sending 
file has LRECL=80 and 

BLKSIZE=3120.



2) The File must be sent as BIN both sides.



3) You might be unblocking the file by specifying an LRECL and BLKSIZE that are 
the same. For example 

LRECL=80 and BLKSIZE=80. This creates a larger file.







So I sometimes on the receiving side pre-allocate the file with LRECL=80 and 
BLKSIZE=3120.







The data needs to be FTP'd with BIN for everything. A TSO XMIT file is not an 
ASCII file. it needs to 

be treated with BIN in FTP process. Otherwise you will corrupt the TSO XMIT 
files records.







Let me know what your file looks like.







Lizette











-----Original Message-----



>From: Bharath Nunepalli 



>Sent: Nov 10, 2015 4:04 PM



>To: [email protected]



>Subject: Re: RECEIVE command in z/OS



>



>Hi Ed,



>



>The input file attributes are: DSORG=SEQUENTIAL, RECFM=VB, BLKSIZE=132, 
>LRECL=128, File 

size=X'001BD216'K bytes



>



>I have tried at first without providing DCB parameters for Output dataset, but 
>the job has end with 

Allocation failure.



>IGD17279I 2 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE SUFFICIENT SPACE 
>(041A041D)



>



>So, my Storage Admin has suggested to provide Space Allocations for the Output 
>dataset. And, I have 

mentioned BLKSIZE with that.



>



>



>The confusing part here is the size of the Output dataset.



>Input dataset is 1.7 GB, but the Output dataset is 8.1 GB.



>Do you think this happened due to BLKSIZE(132) value??



>If yes, it would be really helpful if you provide more details reg the 
>'Unblocking' if I provide 

BLKSIZE value.







----------------------------------------------------------------------



For IBM-MAIN subscribe / signoff / archive access instructions,



send email to [email protected] with the message: INFO IBM-MAIN




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to