OA23478: SECONDARY LANGUAGE SUPPORT AND XML ENHANCEMENTS

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Secondary language support and XML enhancements.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users that install IBM Tivoli Web Access *
  *                 for Information Management 5698WAI00 HOYB320 *
  *                 are affected.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Enhancements were made to allow HTML    *
  *                      generated form Data Model Records(DMRs) *
  *                      to obtain the field, layout, group, and *
  *                      table descriptions from a external file *
  *                      stored in a directory.  Also changes    *
  *                      were made to allow xml to be generated  *
  *                      from DMRs and for transaction           *
  *                      processing to return results in xml     *
  *                      instead of html.                        *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  ****************************************************************
  Labels that appear in the HTML can now come from an external
  file and be used instead of the labels in the DMRs.  The
  language file is coded in the BLQPARMS file using the
  directive Language_File and the explicit path to a file.
  The format of the language file is as follows:
  -
  Note: Comments in the language file start with a !! The file
  is not column specific.  It uses words and ignores white
  space:
  -
  **** For alternate field (DAR) labels ****
      dar_name  hhhh  string
  Example:
      BLG&APST  12DF  Approval status
  The 1st word is the dar_name.  And anytime that DAR is
  used in a layout the value used for 'string' will be
  used.  The hhhn value is required and must be a valid
  hex value.  It is not used but if actuate it will be
  helpful when looking at the html generated since the
  hhhh value (s-word) is what is used in the html and not
  the actual DAR name.
  -
  **** For alternate field Page layout labels *****
  A DVR contains the lay out name that appears at the top
  of the html page, in the html title tag, and the left side
  navigation pain.  To use label from the language file:
       dvr_name.id 6666 string
  Example:
     BLQVPEOP.00  6666  Summary
     BLQVPEOP.01  6666  User Information
     BLQVPEOP.02  6666  Contact Information
  -
  The 1st word is the DataView and a dot and the 'Field List
  ID' that appears on the 'Desktop Panel Layout Definition'
  panel BLGLTSIN when updating a DVR using 3270.  The 6666
  must be used.
  -
  **** For alternate Group labels ****
  A DVR contains the Group label that appears in the legend
  of the 'box around the group' of fields in a html page.
  -
  To use label from the language file:
     dvr_name.group_name 5555 string
  Example:
     BLQVPEOP.SUMHIST   5555  Record History
     BLQVPEOP.PEOPLE    5555  User Data
     BLQVPEOP.CONTACT   5555  Contact Data
  -
  The 1st word is the DataView and a dot followed by the
  'Group ID' that appears on the 'Desktop Field Group Entry'
  panel BLGLFGIN when updating a DVR using 3270.  The 5555
  must be used.
  -
  **** For alternate Table labels ****
  A DVR contains the Table label that appears in the legend of
  the 'box around a table' when a list processor table is
  shown on an html page.
  -
  To use label from the language file:
     dvr_name.table_name 4444 string
  Example:
     BLQVPEOP.SAVESRCH  4444  Search record type
     BLQVPEOP.TRANHIST  4444  Transaction ID
     BLQVPEOP.DELEGATE  4444  Delegated change approver
  -
  The 1st word is the DataView and a dot followed by the
  'Table Name' that appears on the 'Desktop Table Definition'
  panel BLGLTBDL when updating a DVR using 3270.  The 4444
  must be used.
  -
  **** Using dual values for drop down fieds ****
  It is also possible to store data in the record using a
  primary and alternate value.  This only works for Drop down
  (html <select>).
  -
  Note: To be able to display the only the primary or only the
  secondary you must have two web access servers.
  -
  To use this change update the 'Reply meaning' and make is
  'WORDS' and the 'Reply value' 0002 (two words).  Then in the
  DAR 'Validation data basic.' panel enter each possible
  (single) word value:
  -
     BLGLVLSB            VALIDATION DATA ENTRY
       Validation              Entry
         Entry              Description
       Yes______     customer was contacted________
       No_______     customer was NOT contacted____
       Oui______     On a contact  le client_______
       Non______     On n'a pas contact  de client_
       _________     ______________________________
  -
  Next in the language file for the English server would have
  ONLY the English values after the dar_name dot, then valid
  hex number (again s-word might be helpful) followed by the
  primary value and alternate value.  These are the actual
  values that will be stored in the field.
  Example:
     BLQ&YNAP.YES 1111 Yes Qui
     BLQ&YNAP.NO  1111 No Non
  -
  In the language file for the French server would have:
  Example:
     BLQ&YNAP.OUI Yes Qui
     BLQ&YNAP.NON  No Non
  -
  Note: You could have put the description in the language
  file and they would replace the one in the DAR:
  
  BLQ&YNAP.OUI Yes Qui - On a contact  le client
  BLQ&YNAP.NON  No Non - On n'a pas contact  de client
  The - (dash) is required.
  -
  To control which value is shown in display only fields code
  the dar_name dot, hex number (again s-word might be helpful)
  followed a 1 to display the primary value or a 2 to show the
  alternate value.
  -
  Example:
     BLQ&YNAP.    1111 1
     BLQ&YNAP.    1111 2
  -
  Other Notes: You must have the language_file directive code
  in BLQPARMS to turn on the alternate labels and the dual
  values.  You can use the alternated labels without using the
  dual values.  Also Web Access uses static HTML and that must
  be translated manually - the language file only supports
  generated html from DMRs.
  -
  The XML support is enabled by coding xml=1 in HTML post
  data.  When xml=1 is found BLQHXMLC.xml is returned instead
  of the normal html for update and create.  For search and
  retrieve you must supply the xml templates to be used.
  

Problem conclusion

Temporary fix

Comments

• See Problem Summary.
  

APAR Information

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

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

  UA38860

Modules/Macros

• B$QDDXML B$QHL31A B$QHREAD B$QWCINI B$QWCSAY
  B$QWHGEN B$QWPSRL B$QWRGET B$QWRINQ B$QWRNEW B$QWRUPD B$QWRVAL
  B$QWRXML BLQDDXML BLQDOBUS BLQFRTYP BLQGPOOL BLQHL06  BLQHL31A
  BLQHREAD BLQHXMLC BLQNLSLD BLQUPOOL BLQWCINI BLQWCSAY BLQWHGEN
  BLQWPSRL BLQWRGET BLQWRINQ BLQWRNEW BLQWRUPD BLQWRVAL BLQWRXML
  

Fix information

• Fixed component name

  WEB ACC FOR INF

• Fixed component ID

  5698WAI00

Applicable component levels

• R320 PSY UA38860

     UP08/01/15 P F801

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.