Re: job CCSID versus default CCSID, Interactive job name=device?

Bruce,

Thank you. That helps. 

In this case the command should always be issued from the command line. This is 
for a product installation routine, so I don't think the "traveling user" 
scenario will be a problem.

THANKS again,
-Marty

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

date: Sun, 25 Jun 2006 12:32:06 -0500
from: Bruce Vining <bvining@xxxxxxxxxx>
subject: Re: job CCSID versus default CCSID, Interactive job
        name=device?

Marty,

You seem to have a good grasp of the situation.  If the job CCSID is not 
65535 then the default job CCSID will always be set to the job CCSID.  If 
the job CCSID is 65535 then the default CCSID will be based solely on the 
language ID of the job.  If you are confident that the device CHRID will 
always be in synch with the langid of the job then you should be OK (but 
watch out for users traveling from one location to another where each 
location has a different device configuration).

For interactive jobs, the job name is the same as the name of the 
workstation or emulator session that you signed on to.

Do your users run the command directly from the command line?  If not, you 
may also want to check out the CHRIDCTL job attribute.  This defaults to 
*DEVD (take data from the device as is -- what you are currently seeing), 
but can also be set to values such as *JOBCCSID, *USRPRF, and *SYSVAL 
which can be used to have i5/OS do conversion from the device CHRID to a 
more appropriate CCSID.  This works well for display files, panel groups, 
and program prompted commands; but can be massively confusing when used in 
conjunction with the command line for user entered commands (for either 
direct execution or prompting from the command line).  If your users use 
the command line just ignore this paragraph.  If you prompt the comand for 
them you may want to play with the CHRIDCTL parameter. 

And not really relevant to your current situation but, for others who may 
come across this note, CHRIDCTL can also be specifed as the CHRID value 
for CRTDSPF and CRTPNLGRP -- providing a more granular solution than a job 
attribute for those not using commands for data entry.

Hope this helps,
Bruce Vining