EnterpriseOne Release 8.9 Installing and Running the Convert CCSID Tool PeopleBook

Transcription

1 EnterpriseOne Release 8.9 Installing and Running the Convert CCSID Tool PeopleBook September 2003

2

3 Copyright 2003 PeopleSoft, Inc. All rights reserved. All material contained in this documentation is proprietary and confidential to PeopleSoft, Inc. ("PeopleSoft"), protected by copyright laws and subject to the nondisclosure provisions of the applicable PeopleSoft agreement. No part of this documentation may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, including, but not limited to, electronic, graphic, mechanical, photocopying, recording, or otherwise without the prior written permission of PeopleSoft. This documentation is subject to change without notice, and PeopleSoft does not warrant that the material contained in this documentation is free of errors. Any errors found in this document should be reported to PeopleSoft in writing. The copyrighted software that accompanies this document is licensed for use only in strict accordance with the applicable license agreement which should be read carefully as it governs the terms of use of the software and this document, including the disclosure thereof. PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and Vantive are registered trademarks, and Pure Internet Architecture, Intelligent Context Manager, and The Real-Time Enterprise are trademarks of PeopleSoft, Inc. All other company and product names may be trademarks of their respective owners. The information contained herein is subject to change without notice. Open Source Disclosure This product includes software developed by the Apache Software Foundation ( Copyright (c) The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PeopleSoft takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation.

4

5 Introduction Table of Contents INTRODUCTION...6 BEFORE YOU BEGIN...7 INSTALLATION...8 Installing the CCSID Conversion Tool...8 ALTER TABLE OPTION...10 Changing the target CCSID values...10 To convert CCSID using Alter Tables...11 COPY TABLE OPTION...12 To convert CCSID using Copy Table...12 AUDIT A LIBRARY...16 Page 5

6 Introduction When tables were created through the World software, half of the alpha columns in the table were flagged with CCSID Prior to Release 8.9, OneWorld handled these columns with the Translate and Do Not Translate ODBC data sources. Tables in a Translate ODBC data source used IBM Client Access translation algorithms to translate data from EBCDIC to ASCII when reading from a server, and translate from ASCII to EBCDIC when writing to the server. Processes running on the server (CallObj Kernel; UBEs) did not need to do translations, as they were running in EBCDIC and the data was stored in EBCDIC. In Release 8.9, we are using algorithms similar to the Client Access algorithms, provided by IBM as part of SQL on the server, to translate from the country specific codepage (for example, 37 for USA English) to Unicode. The OneWorld code base in Release 8.9 is Unicode, and all strings and characters must be translated to Unicode before passing them into the Release 8.9 code base. The IBM algorithms will NOT translate any columns flagged with CCSID 65535, therefore the CallObj Kernels and UBEs would not be able to read alpha data from these tables. Page 6

7 Before You Begin Before You Begin The following procedures and considerations must be done before running this tool: Must be at V5R1 or later Back up all libraries that are to be converted Page 7

8 Installation Installing the CCSID Conversion tool is the first process to converting the data. Installing the CCSID Conversion Tool 1. Sign onto your AS/400 as QSECOFR. 2. Create a temporary library in which to place the software from the download by entering the following command: CRTLIB JDETEMP 3. Create a save file (SAVF) for the software in preparation for the transfer by entering the following command: CRTSAVF JDETEMP/CCSIDCONV 4. On the machine you have downloaded the one-off to, open a DOS window, then open a file transfer protocol (FTP) session connecting to the AS/400 machine you are using for your enterprise server, and enter the following commands: c:\>ftp youras400name User <youras400name:<none>>: qsecofr [Enter password.] Password: 5. Change directory to the JDETEMP library on the AS/400 by entering the following command: ftp:> cd jdetemp [ jdetemp is current library.] 6. Change the local directory to the directory containing the AS/400 SAVFs using the lcd command, as shown below: ftp> lcd c:\oneworld Fixes\CCSIDCONV [Your local directory is now c:\oneworld Fixes\CCSIDCONV.] 7. Change the mode of transfer to binary by entering the following command: ftp> binary 8. Upload the CCSIDCONV SAVF to the AS/400 by entering the following command: Page 8

9 Installation ftp> put CCSIDCONV 9. Close FTP by entering the following command: ftp> quit 10. Restore the library containing the tool by entering the following commands: RSTLIB SAVLIB(CCSIDCONV) DEV(*SAVF) SAVF(JDETEMP/CCSIDCONV) 11. Before running the tool, rebuild the system SQL cross-reference tables by entering the following commands. Note: These commands can only be executed when the system is restricted. As a result, the system should first be brought to a restricted state with the ENDSYS or ENDSBS commands. ENDSBS *ALL *IMMED Monitor the QSYSOPR message queue, wait for the message System in restricted state then enter: RCLSTG *DBXREF (This command will take from 15 minutes to several hours, depending on the number of data libraries.) 12. To make sure the cross-reference tables are okay after the rebuild, go into STRSQL and enter the following commands: SELECT * FROM SYSTABLES SELECT * FROM SYSCOLUMNS 13. Make sure there are entries in both of these. If there are no entries, contact IBM. 14. The user profile that is use to run any of these tools must be defined with CCSID 37. For example, if you are going to run as QSECOFR, enter the following: DSPUSRPRF QSECOFR 15. If necessary, change the CCSID that QSECOFR is currently using: CHGUSRPRF QSECOFR CCSID(37) 16. Sign off and sign back on again with the following commands: ADDLIBLE CCSIDCONV GO G96CCSID Do not try to run the tools while deleting, restoring or renaming data libraries. After deleting, restoring, or renaming libraries, wait for the QDBSRVXR QDBSRVXR2 jobs to show 0 CPU utilization before proceeding. Page 9

10 Alter Table Option This command changes the definition of the alpha columns in the tables from CCSID to the CCSID you choose. It does not touch the data in the tables. You must have *ALLOBJ or *OBJALTER rights to all the tables in the library in order to run this option. Back up the libraries before you start. Changing the target CCSID values The commands J96ALTER and J96ALTERS have a list of allowed values for the target CCSID. If your target CCSID is not in this list, you will need to change the commands using the following steps: 1. STRPDM option 3 library CCSIDCONV, file QCMDSRC. 2. Key in the source type CMD in the Type column. 3. Take option 2 against the J96ALTER and J96ALTERS members. 4. Prompt (P in the line number or position within the text and press F4) the CCSID keyword. Add your target CCSID to the list of allowed CCSIDs. 5. Press F3, and then Y to save your changes. 6. Type in option 14 next to both commands, and press enter. The double byte CCSIDs have special coding in the tool to assign the corresponding single byte CCSID to columns too short to have the double byte CCSID assigned to them. If your double byte CCSID is not in the list of allowed CCSIDs in the command that was shipped, you are not able to use this tool against your database. Run the Alter Table process against your OneWorld Data Dictionary library as well. Note: The Alter Table process causes updates and COMMITs to the system SQL cross reference tables. A lot of concurrent update activity against the system cross reference tables sometimes causes corruption of these tables. Try not to restore, delete or rename data libraries on your AS/400 while running the Alter Table process. If you need to restore your data library and re-run the Alter Table process, wait for the QDBSRVXR2 process to quiesce before proceeding. On WRKACTJOB toward the Page 10

11 Alter Table Option bottom of the display, you can see the amount of CPU this process is using. Wait for it to fall to 0%. To convert CCSID using Alter Tables 1. On the AS/400, determine your target CCSID. For Western European, this usually will be 37. If you are not sure, look at the Client Access data source jobs (QZDASOINIT in subsystem QSERVER), and see what CCSID they are running with. 2. The Alter Table process adds an entry to your System Reply List: 943 CPA32B2 C This prevents the job from issuing an Inquiry message for each table that it cannot alter (see errors below). 3. Take option to run Alter Table against a library. It will take approximately ½ - 1½ hours for Business Data (2,800 tables in Business Data much faster for less tables depends on the speed of your AS/400). The default is to submit the alter process to batch. Repeat this step for each library that needs converting. It changes the logging level of that job to (4 10 *SECLVL). 4. Examine the report. The tables that failed are at the top of the report (status 50). The tables that completed with warnings are next at status 40. Failures and warnings ask you to examine the joblog. Display the joblog, and search for the table name that failed. Look at the tables that failed. Most usual cause of errors is that the table is not a co-existence table (OneWorld doesn t know about it), and its format is not compatible with SQL. Check whether the table is a OneWorld table. If it is, you may need to use the Copy Table method to convert it. Typical errors: Status 50: Alter table may cause a loss of data in column xxx Status 40: CHGPF MAXMBRS(1) cannot complete because there is more than one member in the file Page 11

12 Copy Table Option To convert CCSID using Copy Table 1. Sign onto the Deployment Server in the JDEPLAN environment. 2. Create new data sources for Business Data, Control tables and Common library pointing to new (empty) libraries you created on the AS/400 (for example, CRPDTAN, CRPCTLN). 3. Copy the source environment (for example, PD7333). Change the default table mapping for new environment to your new Business Data xxx data source. 4. Filter on OCM rows for the new environment for Control Tables, and change to your new Control Tables data source. Change the Common mappings to point to your new Common data source. 5. In the new environment, inactivate the old mappings for these data source, and activate the new OCM mappings that you just added. 6. Go into OMW and create F0004 and F0005 in the new Common or Control Table data sources wherever you have them mapped to, (this is to prevent R98403 from unnecessarily copying all the UDCs into your new version of F0004 and F0005). 7. Create a new version of R98403 (copy XJDE0001 and change it) with the following options: Page 12

13 Copy Table Option Change the record selection as follows: 8. Run the new version of R98403 to create a set of skeleton data sources with empty ERP tables in them. Those tables, which are usually shipped with predefined data in them (for example, F0002), will have the J.D. Edwards data in them. If you have the corresponding table in your input data source, your data overrides the J.D. Edwards data. Page 13

14 9. On the AS/400, sign on as a user who has *ALLOBJ or at least *OBJMGT rights to the tables in the target library. Then ADDLIBLE CCSIDCONV. Go to menu G96CCSID. 10. Determine whether your Client Access datasource jobs (QZDASOINIT jobs) are running with the default ERP CCSID CCSID 37 for Western European; CCSID 937 for Traditional Chinese, CCSID 935 for Simplified Chinese. If you are running with something other than the default (for example, running with German CCSID 273), you need to run the ALTER TABLE to alter your CCSID columns to the CCSID you are using (for example, 273 for German) before doing the Copy Table process. 11. Set up your JOBQ to multi-process (CHGJOBQE QBATCH QBATCH MAXACT(?)). This should at least be set to the number of CPUs that you have in your AS/ Take the menu option to Copy tables, supplying source and target library names for each set of data sources for example, CRPDTA CRPDTAN. You can override the queue to which the jobs are submitted. You can run the command just for one table, or for all tables (all tables is the default). This menu option ties up your green screen while it finds all the tables in the source library, does some basic checking, and then submits a CPYF job for each table. You will get back control while all the submitted jobs are running, and you must monitor to see when they have all completed (WRKSBMJOB *JOB). 13. Once all the copy table jobs have finished for a particular pair of libraries (use WRKJOBQ QBATCH or WRKSBSJOB QBATCH), take the menu option to report on Copy Table. 14. Print out the report. It is sorted in descending order of error severity: A. Run status 50 severe error. i. For authority errors, check the interactive joblog of the job where you ran the Copy Table option (the Copy Table option puts the joblog into a spool file, so it will still be there even if you signed off). ii. For CPYF failures, look at the joblog of the submitted job for that table. The job has the same name as the table. Most usual problem is that the source and target tables have a data item defined differently for example, the data item is defined as character in the source, and as Packed in the target. This would happen if your co-existent database did not match the Xe/ERP 8.0 spec.s. Sometimes this is caused by a table conversion failing during the application of the co-existence PTF. Usually this would indicate that you are not using this table. B. Run status 40 Warning Record Count mismatch. This is usually caused by duplicate records in the table. Look at the joblog of the submitted job for that table it will say which records in the source table could not be copied because they are duplicates. This is caused by the OneWorld definition of the table having different unique keys than the co-existence definition. Make sure that you have the correct version of each of the duplicate rows in your target table. Page 14

15 Copy Table Option C. Run status 30 - CPYF succeeded D. Run status 20 any text. This status indicates that the CPYF is still running. Usually you would only see this if you ran the Copy report while the submitted jobs are still running. Check to see if there is a joblog for this table (job name = table name). E. Run status 15 - CPYF warning - input empty, output not empty. This is most likely normal. R98403 copies J.D. Edwards supplied data into certain tables (for example, F3009, F4009). Check each of these tables in the source library to make sure that the source table really is empty. (You would also see this message if you don t have authority to read the source table.) F. Run status 10 i. No action - input table empty. This is normal. If both source and target tables exist and both are empty, the process does nothing. ii. No action source file. This is normal. There are no source files defined in Xe/ERP 8.0 as tables. G. Run status 05 - Table not in target library. This is normal. Any tables, which are World, only (for example, F93100) will not exist in the ERP - only target library. If your R98403 failed, or if you have a mismatch between your source and target libraries (for example, you are trying to copy tables from Common into Control Tables), you would see this error and would need to correct it. Page 15

16 Audit a Library On the AS/400, take the option to audit a library off the G96CCSID menu. It produces a report of tables in a library which have CCSID columns. This option provides confirmation just before the B9 upgrade that your clean up process has not been inadvertently undone by a restore. This report shows the following statuses: 80 Table still has CCSID columns. Run the J96ALTERS process. 70 Table has CCSID columns, but the J96ALTERS process will not fix them. (This could be because the table is an AS/400 source file or because ether table was created through SQL. This process only works on tables created through DDS.) If there are other statuses in the audit table from a previous run of the ALTER or the COPY TABLE process, and you choose the option to print all tables (not just the ones found to still contain CCSID 65535), you may see other statuses in the report. These relate to the previous ALTER or COPY attempt against this library. Only status 70 and 80 are relevant to the audit process. Page 16