Reason:
This message is issued in response to a selected module loaded by MUF or DBUTLTY. The execution EXEC JCL statement can include a parameter of PGMDT= or PGMMONTH=1. The module has a date equal to or later than the value displayed. The message that is issued in the MUF job for DBSRPPR matches the message that CA Datacom/DB issues. The message is also issued each time DBSQLPR is used.
In the message text:
(Optional.) is a parameter contained in the execution EXEC JCL statement.
Note: In DBSQLPR output, there is no parameter named PGMDT= (or PGMMONTH=1). In DBSQLPR output, this field is therefore blank.
The ccyymmdd represents:
The default date is a date that is close to the GA date.
On the EXEC PGM= JCL statement, if you specify nothing, to include everything in the output, CA Datacom/DB and SQL DBSRPPR takes a default date around the GA date. If you specify PARM=’/PGMDT=20121010’, however, both CA Datacom/DB and SQL DBSRPPR use that date to compare against, and anything later is displayed.
is the load module name.
is only displayed when DBSRPPR for SQL is displayed as the load-mod-name. The DBSRPPR load module contains numerous executable modules.
ccyy/mm/dd is the date and hhmm is the time either of the assembly or compile of the program name (if there is one) or the assembly of the module name. In MUF, a default is applied that is a date close to the time the product was made generally available (GA). For example, if DBSRPPR(AGGEXEC) is displayed as the load-mod-name(program-name), the displayed date and time can be:
is the release of the module, that is, the release of the product, for example 14.0.
is the latest PTF applied to this load module or program name, if there is one.
Action:
None. This message is for information only.
|
Copyright © 2014 CA.
All rights reserved.
|
|