Now, THAT one I have done. Had to, after the first attempt to go Production. The utility worked, just flagged a TON of stuff as bad. We accepted that and kept going. Cleaning up the v3.5 history and checkpoint files first will allow a successful fallback. Having to rerun VINIT to get the right internals loaded is a pain in the a$$, tho. I'd much rather the product load the damn internals when it starts, and quit screwing around with VINIT. Oh, and GSSA had to be active during the conversion, each way. And for the VINIT. Joy.
Steve Conway Lead Systems Programmer Information Systems & Services Division Computer & Network Operations Phone: (703) 450-3156 Fax: (703) 450-3197 "Carlson, Steven" <steven.carl...@nsc.com> Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> 05/01/2009 12:45 PM Please respond to IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> To IBM-MAIN@bama.ua.edu cc Subject Re: Using CA-JOBTRAC V11 SP3 in Production One of my pre-reqs for JOBTRAC V11 is to be able to fall back to JOBTRAC V35. I am still working on this problem with CA, because I am unable to convert the database back to V35 format. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
