Description :Extension and modification of the General Calendar can be time consuming. After modification of the General Calendar it should be deployed to the entire park of DUAS v5.6 nodes.
Cause
Cause type: Configuration Root Cause: The General Calendar can not be deployed to an MU
Environment
OS: All
Resolution
This procedure is for DUAS v5. In DUAS v6 the General Calendar can be deployed from UVC. Procedure to export the General Calendar (indicated by " 00" - space, zero, zero) to a file and subsequent import to remote nodes. All commands are executed on the (reference) node where the modified General Calendar has been prepared
It is recommended to stop the Calculator and Launcher on critical nodes before importing Calendars.
Please test the following procedure on a limited set of preprod nodes before using it in production.
A. Extract the General Calendar to a file:
./uxext CAL MU=" 00" OUTPUT=GENERAL_CALENDAR.ext
B. Insert the General Calendar into one other node:
./uxins CAL MU=" 00" CIBLE=" 00" INPUT=GENERAL_CALENDAR.ext node=vmstl64c63 REPL
C. Insert the Calendar into a list of nodes: WARNING: The sequence below has to be executed once for each Company 1. Generate a text file (node_file.txt) containing all the node names (one on each line) -Use the following command: ./uxlst NODE | awk '{ print $1 }' > node_file.txt - Then open node_file.txt and remove the first 4 lines manually
2. Run the script below -Paste the lines below in a file (CAL_script) and make it executable (chmod 777 CAL_script) -Run the script by: ./CAL_script
Script lines to be pasted in CAL_script:
#!/bin/ksh file="$UXEXE/node_file.txt" # while loop while read node_name do echo "$node_name" ./uxins CAL MU=" 00" CIBLE=" 00" INPUT=GENERAL_CALENDAR.ext node=$node_name REPL sleep 1 done