ARFC GFSv16.3.8 - add debug flag to resolve wave post runtimes

[KateFriedman-NOAA]

Description

The wave post jobs were running long in production. GDIT added the ldebug PBS statements to the wave post ecf scripts to resolve the issue.

This change became GFSv16.3.8 in operations via an ARFC.

Will merge the auth repo release/gfs.v16.3.8 into the dev/gfs.v16 branch after this goes in since it was already implemented in ops via an ARFC.

Refs #1843

Type of change

Operations update (accelerated).

Change characteristics

• Is this a breaking change (a change in existing functionality)? NO
• Does this change require a documentation update? NO

How has this been tested?

Tested in para ops by NCO/GDIT.

Checklist

• Any dependent changes have been merged and published
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• New and existing tests pass with my changes
• I have made corresponding changes to the documentation if necessary

[JessicaMeixner-NOAA]

Perhaps unrelated, but can we add something similar for rocoto in the develop branch? We're seeing these issues with the top of develop as well and it'll be a bit before we get this job refactored.

[KateFriedman-NOAA]

Perhaps unrelated, but can we add something similar for rocoto in the develop branch? We're seeing these issues with the top of develop as well and it'll be a bit before we get this job refactored.

@JessicaMeixner-NOAA Yes, pretty sure we can. We already set a debug flag (debug=true) for all jobs on WCOSS2 (when scheduler = pbspro) so can likely do something similar with the native tag in the rocoto xmls for the wave post jobs to add ldebug=true. Will open a separate issue to do that.