EQQ0398E EQQ0420E
EQQ0398E UNSUCCESSFUL PUT
SYNAD1
Explanation: An error occurred while writing to an intermediate work file or the track log file used by daily planning.
The SYNAD routine extracted the following information: job name, stepname, unit address, device type, ddname,
operation, error description, phys-DA, and access method.
System action: The daily planning program is terminated. A new current plan and reports may have been
produced.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product
installed on this MVS/ESA system.
User response: If no new current plan was produced, correct the error and resubmit the job. If a new current plan
was produced but not reports, correct the error and then use the Replanning Current Plan Period panel to produce the
reports.
EQQ0399I
SYNAD2
Explanation: This message is a continuation of message EQQ0398E.
System action: The daily planning program is terminated. A new current plan and reports may have been
produced.
User response: If no new current plan was produced, correct the error and resubmit the job. If a new current plan
was produced but not the reports, correct the error and then use the Replanning Current Plan Period panel to produce
the reports.
EQQ0401E INVALID DATES GENERATED FOR APPLICATION
ADID
RULE
RULE
Explanation: The long-term plan batch programs encountered invalid dates when trying to generate occurrence run
dates for a rule-based run cycle. Most likely, this is an internal OPC processing error. Note, however, that run dates
already generated for this run cycle should be perfectly valid, and useable. If the run cycle is based on a regular rule
then dates after the failure point will be missing. If it is based on an exclusion rule then dates after the failure point
will not be excluded by this run cycle. Dates generated for the other run cycles of the application are valid, and will
appear in the plan.
System action: The job stops processing the current rule-based run cycle, and continues with the next belonging to
the application.
User response: Debugging information written to the OPC diagnostic file (EQQDUMP) should be forwarded to the
local IBM Representative.
EQQ0405E DATE
DATE
PRIOR TO CURRENT DATE
Explanation: A date specified to TME 10 OPC is prior to the current date.
System action: The job is terminated.
User response: Correct the date and then rerun the job.
EQQ0412E SPECIFIED TIME SPAN IS GREATER THAN 4 YEARS
Explanation: The time span, from current date to end date, may not exceed four years.
System action: If this message is issued from a batch job, the submit request is terminated; if it is issued in the
dialog, the system waits for you to respond.
User response: Specify an end date less than four years from the current date.
EQQ0420E CALENDAR ID NOT SPECIFIED
Explanation: This message is issued from a batch job; the submit request is terminated.
User response: Specify a valid calendar ID.
454 TME 10 OPC Messages and Codes
