The emulator may also be to blame, Tom Brennan's Vista TN3270 has an
option to remove the obsolete EOF (x'1A') from text files upon
z/OS-to-PC IND$FILE, but the initial version containing this option
would also remove the same character (for binary files!) if it
occurred as the last character of a z/OS record in the middle of a
file, which would (for me) cause PCTERSE to loop, writing out files
that on one occasion (I'd been making coffee) reached several tens of
gigabytes.

The bug has long been fixed (at Tom's usual break-neck speed), and I'm
not even sure if it's the stable version, but if the client used a
test version, it's not impossible that this might be the cause.

Robert
-- 
Robert AH Prins
robert(a)prino(d)org


On 2012-12-18 19:57, Scott Ford wrote:> Roger,
>
> IND$FILE also has upload issues , include file location and location unless 
> its per allocated
>
> Scott ford
> www.identityforge.com
>
> Tell me and I'll forget; show me and I may remember; involve me and I'll 
> understand. - Chinese Proverb
>
>
> On Dec 18, 2012, at 2:11 PM, Roger Bolan <[email protected]> wrote:
>
>> Uploading (from workstation to MVS data set) is a step where unintentional
>> changes can easily happen.   Using either FTP or a terminal emulator like
>> Personal Communications, you may have to send SITE commands or set values
>> to control the allocation, both size and DCB attributes) of the  host data
>> set on the receiving end of the upload.   When I have clients send MVS data
>> sets to me, I typically have them terse it first, then do BINARY
>> downloads/uploads and make sure the final target sequential data set didn't
>> end with 16 extents.  For binary FTP upload  of tersed data I specify the
>> space and DCB.  For example:
>> SITE recfm=fb lrecl=1024 cylinders primary=100 secondary=10 blksize=0
>> for the tersed data set.  Then I use JCL for the AMATERSE UNPACK step which
>> pre-allocates a large output data set and releases the extra space.
>>
>> --Roger
>>
>>
>>
>> On Tue, Dec 18, 2012 at 11:31 AM, Binyamin Dissen <
>> [email protected]> wrote:
>>
>>> Yes, I uploaded it.

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

Reply via email to