Yes I do, although JDE and others frown upon it. The technique is a variation on a GATS document called "Object Transfer Between Instances" and I have used it many times.
For one of my clients I wrote up the procedure on an AS400 system (I had two systems, hence all the file copies etc) and I have pasted it in below:
Libraries SYSB733, OLB7333, DDB733, CODEVB733 and DEVB733DNT were backed up from the live B7332 system and restored onto the Xe system box. Additionally the live DEVB733 PathCode was copied via a PC from the live system onto the B733 share on the Xe deployment server. This share still exists and there are packages in place. An Xe workstation was then saved using SnapShot and a DEVB733 Package Deployed to the workstation complete with development objects. Security Server and Lock Manager were then disabled in the JDE.INI file.
From here a configuration was set in B7332 to connect to the Xe system. Firstly the following DataSources were created, and these point to the library indicated:
• System – XE SYS7333
• System – XE – DNT SYS7333
• Object Librarian – XE OL7333
• Data Dictionary – XE DD7333
• Central Objects – DVXE CODV7333
• Versions – DVXE – DNT DV7333DNT
A PathCode was then defined in B7332 called DV7333 at a release level of B733 using the B7333 Share and the Central Objects – DVXE DataSource as the deployment DataSource. Copying DEVB733 then created an Environment called XETRANS and XETRANS was then modified so that the PathCode became DV7333. The OCM was then changed so that Central Objects, Versions, System, Data Dictionary and Data Dictionary all point to the new XE DataSources defined above.
Effectively this process allows B7332 to transfer objects to the DV7333 XE PathCode. What happens in Object Transfer is that the target PathCode is set to DV7333, when the transfer button is hit, the Environment Master is read and the first Environment found with that PathCode entry is used, in this case it will be XETRANS. The OCM for that environment is then read, and together the PathCode definition, the Central Object Records and files on the Deployment Server are transferred to DV7333. The XE Object Librarian is also populated via the OCM entries, so records from OLB733 are copied into OL7333.
This process was tested, and an OMW Project called TRANSFER was created at Status 21 with the JDE Profile as Supervisor, Manager and Developer. B7332 was run and the custom objects transferred across. These were then added to the TRANSFER Project and checked out, these objects are now part of the standard OneWorld XE system.
To do this for real, the following Procedure needs to be run:
• Identify on the B7332 system all Objects and Versions that need to be transferred to the XE system.
• On the B7332 Live System verify that all of these Objects and Versions are in the DEVB733 PathCode. Use Object Transfer to move them if required.
• Backup from the B7332 System Libraries OLB733, CODEVB733, DEVB733DNT and DDB733. Restore these libraries to the XE System. DO NOT restore SYSB733; the existing library contains the definition for the Transfer Environment.
• Copy the B7332 B733\DEVB733 Share (Excluding Packages) from the B7332 system to the B733\DEVB733 share on the XE System.
• Enter DEVB733 on a B7332 machine running from the XE system and enter object Transfer; the menus will not work so run P98604 from the FastPath. Transfer all Objects and Versions to PathCode DV7333, this will probably take some time and is a manual procedure.
• Sign into DV7333 on XE and add all of these transferred objects to a project, TRANSFER is available should it be required. The objects can now be promoted via the OMW rules and packages built accordingly.
NOTE1: This system should not be used for Standard Objects, custom Objects and Versions should be the ONLY objects transferred.
NOTE2: Any custom tables transferred will need to be generated in the relevant DataSource in Xe.
Paul Clark
Independant CNC Consultant
Multiple Clients - All Xe AS400