A quick test on V5R3 shows that the job-level Decimal Format (DECFMT) specification is reflected in the output of the Work with Disk Status (WRKDSKSTS) feature; on the next invocation since the Change Job (CHGJOB) request, irrespective of the WRKDSKSTS parameter keyword specifications [though I could not confirm the difference between 'J' and 'I' for spooled output because the values were never small enough when using OUTPUT(*PRINT)]. Thus it seems, the decimal-point\decimal-separator used for that display is independent of the primary or secondary language being utilized; except how that might play a role in the setup of the establishment of the job settings for a User Profile, but easily overridden nonetheless.

However a system-API should not be dependent on the _displayed_ output from the WRKSYSSTS, so the intended test is doubtful to prove successful... for the alluded possible origin.

Regards, Chuck

On 01-Feb-2014 07:47 -0800, Jack Kingsley wrote:
I was thinking about what Roberto wrote, I also was looking at
chgjob, there is a DECFMT keyword, not sure if that would make a
difference or not. You might be write with the QDECFMT as well, when
you changed it, did you sign off.back on??

On Sat, Feb 1, 2014 at 10:40 AM, Roberto José Etcheverry Romero wrote:

I've seen a workaround to this installing 2924 (english) as a
secondary language and setting it as default for those programs.
Don't ask me how that works, I've seen it implemented only.

On Sat, Feb 1, 2014 at 12:23 PM, David wrote:

I am working with a 3rd party product that uses an API to
retrieve disk status info. The product has worked on other
systems in the past.

I am trying to use it on a system in South America and I think
the application is confused because the percentages are presented
with commas where it expects decimal points.

For example, WRKDSKSTS shows:

Tamano % I/O Request Read Write Read Write %
Unid Tipo (M) Util Rqs Size (K) Rqs Rqs (K) (K) Busy
1 6717 7516 80,9 ,0 ,0 ,0 ,0 ,0 ,0 0
2 6717 7516 80,9 ,0 ,0 ,0 ,0 ,0 ,0 0
3 6717 7516 80,9 ,0 ,0 ,0 ,0 ,0 ,0 0
4 6717 7516 80,9 ,0 ,0 ,0 ,0 ,0 ,0 0
5 6717 7516 80,9 ,0 ,0 ,0 ,0 ,0 ,0 0

I want to prove that this is the issue by changing the "option"
from comma to decimal point.

I hoped that the system value QDECFMT was dictating the value
but changing it from 1 to 3 and back doesn't affect the
presentation of WRKDSKSTS.

Does anyone know what is telling the OS to show the commas rather
than decimal points.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page