|
It does seem contradictory but the first paragraph is talking about
FILETYPEs in general, of which there are two -- *DATA and *SRC. The
second paragraph then says *DATA can't be used which leaves you with *SRC.
And if you play with CRTPF and FILETYPE(*SRC) you will find that CCSID is
used (and CPD7306. CPD7307 being sent in many other cases).
The text could be improved on...
Bruce
rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/26/2006 07:14 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
Re: CRTPF and job CCSID
Is it just me, but does the second paragraph of the help for ccsid seem to
conflict with the first paragraph?
This parameter is applicable only if no value is specified for the
Source file (SRCFILE) parameter and if a value is specified for the
Record length (RCDLEN) parameter. If you specify a value other than
the default value (*JOB) on this parameter, the SRCFILE parameter is
not used, and a value must be specified for the RCDLEN parameter.
Note: A file created with no DDS when FILETYPE(*DATA) is
specified has a CCSID of 65535, regardless of the job CCSID
value.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.