In some situations the Symphony file in IBM Workload Scheduler is
not created. For example, there might be a recovery from a disaster
situation.
In this example, the new current plan is created, but the Symphony file is not. In this
situation, you can keep the current plan up-to-date by selecting the SYMPHONY
RENEW option from the Producing OPC Daily Plans dialog shown below. Figure 1. EQQDPLNP - Producing daily plans
EQQDPLNP --------------- PRODUCING OPC DAILY PLANS ------------------------
Option ===>
Select one of the following :
1 REPLAN - Replan current planning period
2 EXTEND - Extend the current planning period
3 TRIAL - Produce a trial plan
4 PRINT CURRENT - Print statistics for current planning period
5 SYMPHONY RENEW - Create Symphony file starting from Current Plan
Here are some other cases where you renew the Symphony file to
recover from error situations:
There are configuration errors such as: the specified directories
do not exist, the file system is full, or the workstation is not correctly
defined.
The workstation definitions are incorrect.
An incorrect Windows™ user
name or password was specified.
Job EQQPCS05 is
run to create the work directory (WRKDIR) or the
Symphony file was deleted (rm command) or renamed (mv command) from WRKDIR.
TCP/IP goes down after the Symnew file
is created but before it is switched. When TCP/IP is restarted, the
end-to-end server is not able to switch the Symphony file.
There are also regular operation situations when you need to renew
the Symphony file, such as:
You change the TCP/IP port number on a workstation.
You modify the CPUREC or DOMREC initialization
statements.
Note: Each time you add a new CPUREC statement,
you must define the new agent in the workstation (WS) database and
submit a CP EXTEND or a CP REPLAN job,
but not a Symphony Renew.
You add or change a USRREC statement
(including USRCPU, USRNAM, USRPSW).