IJ15089: CHANGING LANG IN KSH JOBS CAUSES SEARCH PERFORMANCE AND MISMATCH

APAR status

• Closed as fixed if next.

Error description

• Scripts performing a large number of pattern matching
  operations will be very slow if the LANG changes after
  the start of the script.
  
  For example, pattern matching such as this -
  
  [[ "$line" = +([!:])::* ]]
  
  - will be slow if the script starts with LANG=en_US and
  is then switched to C.
  
  
  Also the following would fail to find and operate if
  there are Japanese directory/files if in the middle of
  the job LANG changes to JA_JP.
  #!/usr/bin/ksh
  
  export LANG=JA_JP
  chown -R user1 /users/common/*
  

Local fix

• Do not change environment LANG in KSH scripts
  

Problem summary

• Changing the LANG from inside the script causes performance hit
  and a mismatch
  

Problem conclusion

Temporary fix

• Please change the LANG before running the script.
  

Comments

• This APAR is being closed FIN. This means that a solution to
  this APAR is expected to be delivered from IBM in a release
  (if any) to be available within the next 24 months.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels