Welcome to the Intranet Prayer Groups
Public Relations and Social Media |
How To Copy Assist Live To Assist Proof And Back AgainBefore attempting the copies below you must turn off the asyncs. You may even have to stop Tomcat on WebStore if there is a file lock. See the bottom of this page for instructions on how to find a file lock. Below are the files that need to be copied from production to proof. When ready with these files, copy them back into production. The commands that are used are listed below. When you copy back to production you will need to reverse the from and to libraries:
Commands used from the Assist command line: CPYF FROMFILE(ASTDTA/OEPRCFOJ) TOFILE(ASTPROOF2/OEPRCFOJ) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/ICPRTMIA) TOFILE(ASTPROOF2/ICPRTMIA) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/OEBILMIF) TOFILE(ASTPROOF2/OEBILMIF) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/OELSHDLK) TOFILE(ASTPROOF2/OELSHDLK) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/OELSDLLP) TOFILE(ASTPROOF2/OELSDLLP) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/ICAPRTCP) TOFILE(ASTPROOF2/ICAPRTCP) MBROPT(*REPLACE) For the quickest way to do this: After typing the command once, use F9 to bring the last command back to the command line and then simply change the filename being copied. For WebStore Files:
CPYF FROMFILE(ASTDTA/SFCPRLCX) TOFILE(ASTPROOF2/SFCPRLCX) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/SFCTXTCT) TOFILE(ASTPROOF2/SFCTXTCT) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/SFPTXTPT) TOFILE(ASTPROOF2/SFPTXTPT) MBROPT(*REPLACE) CPYF FROMFILE(ASTDTA/SFPMMDPM) TOFILE(ASTPROOF2/SFPMMDPM) MBROPT(*REPLACE) Notes:
How to Find a File LockIf the copy message says it can't clear the file it must be due to a job that is locking the file. Use WRKOBJLCK OBJ(OEPRCFOJ) OBJTYPE(*FILE) This should display the job(s) that is locking the file. It very well may be an empty list but notice if a highlighted message at the bottom displays Press F6 to see member locks. Press F6 and you will be able to view the job that is likely locking the file. If it is the job QZRCSRVS by user QUSER then it is a WebStore connection problem. That job must be killed. |