PK93020: BF 7.1.1 slow export with MySQL and in-line projects

APAR status

• Closed as program error.

Error description

• BF 7.1.1 slow export with MySQL and in-line projects
  
  The export process should only go after valid project data - not
   build data. In 7.1.1 we see the following excerpt in the export
   of a large complex project with in-lines:
  
  ...
  28716 PRE:[SELECT bf_value FROM bf_sysconfig WHERE bf_param='sch
  ema_version']
  28716 PRE:[SELECT * FROM bf_steps b WHERE bf_project_id=? ORDER
  BY bf_seq]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  28716 PRE:[DELETE FROM bf_store where bf_id=?]
  28716 PRE:[INSERT INTO bf_store (bf_id, bf_part, bf_hex, bf_text
  ) values (?,?,?,?)]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  28716 PRE:[SELECT * FROM bf_projects WHERE bf_id=?]
  28716 PRE:[SELECT * FROM bf_steps b WHERE bf_project_id=? and bf
  _active='Y' ORDER BY bf_seq]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  28716 PRE:[SELECT b.bf_enabled, s.bf_text FROM bf_buildsteps b,
  bf_store s WHERE b.bf_stepid_store = s.bf_id AND b.bf_build_id=?
   AND s.bf_text=?]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  28716 PRE:[INSERT into bf_buildenv (bf_id,bf_level,bf_name,bf_or
  igenv_id,bf_root_id) values (?,?,?,?,?)]
  28716 PRE:[SELECT count(*) AS bf_exists FROM bf_sysconfig WHERE
  bf_param=?]
  28716 PRE:[UPDATE bf_sysconfig SET bf_value='1', bf_title=? WHER
  E bf_param=? AND bf_value='0' AND bf_title='']
  28716 PRE:[SELECT bf_value,bf_title FROM bf_sysconfig WHERE bf_p
  aram=?]
  28716 PRE:[UPDATE bf_sysconfig SET bf_value='0',bf_title='' WHER
  E bf_param=?]
  28716 PRE:[INSERT into bf_buildenventry (bf_id, bf_env_id, bf_se
  q, bf_param, bf_value_store, bf_action) values (?,?,?,?,?,?)]
  28716 PRE:[INSERT into bf_buildenv (bf_id,bf_level,bf_name,bf_or
  igenv_id,bf_root_id) values (?,?,?,?,?)]
  28716 PRE:[INSERT into bf_buildenventry (bf_id, bf_env_id, bf_se
  q, bf_param, bf_value_store, bf_action) values (?,?,?,?,?,?)]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  28716 PRE:[SELECT * FROM bf_projects WHERE bf_id=?]
  28716 PRE:[SELECT * FROM bf_steps b WHERE bf_project_id=? and bf
  _active='Y' ORDER BY bf_seq]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  28716 PRE:[SELECT b.bf_enabled, s.bf_text FROM bf_buildsteps b,
  bf_store s WHERE b.bf_stepid_store = s.bf_id AND b.bf_build_id=?
   AND s.bf_text=?]
  28716 PRE:[SELECT * FROM bf_store where bf_id=? ORDER BY bf_part
  ]
  ...
  
  There are UPDATE and INSERT statements which should not exist in
   a bfexport scenario. In addition to being much slower during ex
  port now there are also locking issues with MySQL due to the INS
  ERTs and UPDATEs occurring at the same time as the export.
  
  In my console there are now bf_buildenv entries with no build in
   the database at all.
  
  There are two items which get touched and should not be during a
  n export:
  -Any in-line calls will not maintain the export flag
  -Build environments are created during the export
  

Local fix

Problem summary

• The export process was slowed down due to the creation of
  build environments (which are the result of inline steps not
  knowing they're actually exports).
  

Problem conclusion

• This is fixed in 7.1.1.1, build ?= 46.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  BUILD FORGE EE

• Fixed component ID

  5724S2701

Applicable component levels

• R710 PSN

     UP