Re: New toys

Thank you again, Barbara.  And to expand on this, just to make sure I don't mess it up, with our policy of applying PTFs on development first and then on production after a shakeout period, the sequence would go something like this:

1. Apply PTFs to development
2. ADDENVVAR QIBM_RPG_DISABLE_TIMESTAMP_MICROSEC VALUE('Y') LEVEL(*SYS) on development
3. (normal PTF shakeout period)
4. Apply PTFs to production
5. RMVENVVAR QIBM_RPG_DISABLE_TIMESTAMP_MICROSEC LEVEL(*SYS) on development

Basically, just remember to remove the environment variable on development after you apply the PTFs to production.


On 6/1/2020 6:24 AM, Barbara Morris wrote:

On 2020-05-30 1:16 p.m., Joe Pluta wrote:

Thank you, Barbara!

We're just getting ready to install PTFs our development machine.  I'll get this into our deployment notes.  We can add this as LEVEL(*SYS), correct?

Correct.

For others reading this ...

If you use LEVEL(*SYS), it will be present in every job that starts -after- you add the envvar.

So if you also want the envvar in your current job where you add the LEVEL(*SYS) envvar, you also need to add it the ordinary way in that job (with LEVEL(*JOB)).

ADDENVVAR QIBM_RPG_DISABLE_TIMESTAMP_MICROSEC VALUE('Y') LEVEL(*SYS)
ADDENVVAR QIBM_RPG_DISABLE_TIMESTAMP_MICROSEC VALUE('Y')