×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 23 Aug 2013 13:21, Hoteltravelfundotcom wrote:
What if I change the system value for the duration of my CREATE VIEW
and then change it back?
That would have no effect on the CREATE VIEW in the job issuing the
CHGSYSVAL. The CCSID needs to be established in the job; i.e. whatever
is shown to be set in the following request, is the CCSID that will be
used; notably, the value can *not* be *SYSAVL because the value is
already /resolved/ to an effective numeric CCSID:
CHGJOB ??CCSID()
Would that cause any possible problem?
Changing the system value QCCSID could cause from zero to many
problems. Changing system-wide configurations should be tightly
controlled under System Change Management, and should not be allowed on
a whim in some user job.
On Fri, Aug 23, 2013 at 4:18 PM, Hoteltravelfundotcom wrote:
I changed it [<ed> the CCSID()] on the profile but the create VIEW
is still 65535
The word *future* in the earlier reply [maintained in the quoted text
below] is very pertinent.
On Fri, Aug 23, 2013 at 3:14 PM, CRPence wrote:
<<SNIP>> the easiest resolution is to perform a request to
CHGPRF CCSID(appropriate_value) for which that appropriate
CCSID value will be established for all future jobs started
by that user profile. <<SNIP>>
Thus after the CHGPRF CCSID(chosen_value), either sign-off and then
sign-on with that since-changed user profile, or issue the request to
CHGJOB CCSID(chosen_value) in the same job to mimic what the effects of
having started a new job.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.