Your SlideShare is downloading. ×

Mod05 application migration

90
views

Published on

Application Migration to HP NonStop H- und J-Series Operating Systems

Application Migration to HP NonStop H- und J-Series Operating Systems

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
90
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • NonStop H-Series and J-Series Operating Systems Application Migration Application Migration 5 - Application Migration
  • Transcript

    • 1. Application MigrationApplication MigrationModule 5
    • 2. NonStop S-Series to Integrity NonStopNonStop S-Series to Integrity NonStopMigration PathsMigration Pathsmigration paths:◦ S-series TNS Mode to Integrity NonStop TNS Mode◦ TNS/R Native Mode to TNS/E Native Mode5 - Application Migration 2TNS ModeNative ModeTNS ModeNative ModeS-series System (TNS/R)Integrity NonStop System(TNS/E)
    • 3. NonStop S-Series TNS Mode toNonStop S-Series TNS Mode toIntegrity NonStop TNS ModeIntegrity NonStop TNS Mode◦ Any TNS Guardian program that runs onan S-series platform should run on an IntegrityNonStop with no changes◦ TNS Guardian object codecan be emulated by an interpreter◦ TNS Guardian object code accelerated in TNS/Rsystem can be accelerated again in TNS/E system Object file can contain both accelerated versions◦ TNS execution is not supported in the HP NonStopOpen System Services (OSS) environment5 - Application Migration 3
    • 4. TNS/R Native Mode toTNS/R Native Mode toTNS/E Native ModeTNS/E Native ModeMigrating object code running in TNS/Rnative mode to run inTNS/E native modeusually requires only a recompilation using aTNS/E native compiler, except:◦ In a few cases, source code needs changes For example, conditional compilation: “ if <TNS/R> … else … “ (TNS meant)◦ To incorporate some of the new H- or J-seriesfeatures into the application for performanceimprovement and other benefits◦ Some features considered obsolete in the TNS/Rnative programming languages are not supportedin the TNS/E native version of the language5 - Application Migration 4
    • 5. Preparing Programs for MigrationPreparing Programs for Migration◦ Be sure the program runs successfully on theG06.20 or later G-series ReleaseVersion Update (RVU)◦ If the program runs on an earlier RVU, see thefollowing documents and upgrade: G06.xx Software Installation and Upgrade Guide G06.xx ReleaseVersion Update Compendium Interactive Upgrade Guide and Interactive Upgrade Guide25 - Application Migration 5
    • 6. Maintaining Common Source CodeMaintaining Common Source Code◦ Most TNS/R native programs will require nochanges to migrate them to an IntegrityNonStop system◦ When maintaining a common source code forTNS/R and TNS/E native compilers: Do not use any of the new H- or J-series features Avoid using those few features in the TNS/Rprograms that are not supportedin the H- or J-series RVUs5 - Application Migration 6
    • 7. Alignment of DataAlignment of Data◦ Different compilers align data items differently: TNS compilers align data on even-byte boundaries TNS/R and TNS/E compilers align 4-byte data items on 4-byteboundaries TNS/E compilers also align 8-byte data items on 8-byteboundaries TNS/E native POOL_GETSPACE_, GETPOOL, and mallocprocedures allocate buffers aligned on 16-byte boundaries◦ Programming errors or run-time events can cause adata item to violate the data alignment rules and canchange the behavior of the program.◦ use EPTRACE◦ Applications bound into GDSX must be recompiled.◦ Because of 16-byte alignment in DEFINEPOOL5 - Application Migration 7
    • 8. Adjusting for Increased DCT LimitsAdjusting for Increased DCT Limits◦ The maximum size of the Destination Control Table(DCT) can be optionally increased from 32,767 to65,376 as of G06.23 RVU and H-series The default setting for the extended DCT limit is: OFF for G06.23 or later RVU OFF for H-series RVU (originally proposed to be on)◦ The affected programs are those that call thefollowingC-series procedures: FILEINFO GETDEVNAME GETPPDENTRY GETSYSTEMNAME LOCATESYSTEM LOOKUPPROCESSNAME5 - Application Migration 8
    • 9. Adjusting for Increased DCT LimitsAdjusting for Increased DCT LimitsC-Series Procedure Replacement ProcedureFILEINFO FILE_GETINFOLIST_GETDEVNAME DEVICE_GETINFOBYLDEV_, CONFIG_GETINFOBYLDEV_,CONFIG_GETINFOBYLDEV2_, FILENAME_FINDSTART_,FILENAME_FINDNEXT_GETPPDENTRY PROCESS_GETPAIRINFO_GETSYSTEMNAME NODENUMBER_TO_NODENAME_LOCATESYSTEM NODENAME_TO_NODENUMBER_LOOKUPPROCESSNAME PROCESS_GETPAIRINFO_5 - Application Migration 9To migrate the affected programs:◦ Change programs to use replacement procedures◦ Use SCF to reset the DCT limits extension to ON
    • 10. TNS/E pTAL CompilerTNS/E pTAL Compiler◦ All TNS/R pTAL programs must berecompiled with the TNS/E pTAL compiler.◦ Most of the features and constructs of TNS/RpTAL are supported in TNS/E pTAL, except: Some privileged operations Some features, such as SRL, that are not supportedin H-series RVUs Features considered obsolete in TNS/E pTAL◦ All code produced by the TNS/E compilers isposition-independent code (PIC), which canbe used to create DLLs.5 - Application Migration 10
    • 11. pTAL Compiler DirectivespTAL Compiler Directives◦ Compiler directives that must be removed orchanged: SAVEGLOBALS: not supported USEGLOBALS: not supported NOCALL_SHARED: the compiler generates PIC only NOGP_OK: not needed; SRLs are not supported TARGET:TNS_R_TARGET option is not accepted.Replaced by TNS_E_TARGET◦ Compiler directives that are obsolete and areignored by the compiler (a warning is issued): BEGINCOMPILATION: not supported and is ignored SRL: not supported and warning is issued GP_OK, PUSHGP_OK, POPGP_OK, and NOGP_OK:these SRL-related directives are ignored by the compiler5 - Application Migration 11
    • 12. pTAL Compiler DirectivespTAL Compiler Directives◦ Compiler directives that have differentbehavior and may require source codechanges: OPTIMIZEFILE: warnings are issued in certainconditions OVERFLOW_TRAPS and NOOVERFLOW_TRAPS:In TNS/R pTAL, OVERFLOW_TRAPS is the default,but in TNS/E pTAL, NOOVERFLOW_TRAPS is thedefault5 - Application Migration 12
    • 13. pTAL Functions and ProcedurespTAL Functions and Procedures◦ Functions and procedures that are not supportedand should be replaced with H- or J-seriesdirectly-called privileged interface: $EXECUTIO, $INTERROGATEIO,$INTERROGATEHIO, $LOCATESPTHDR,$LOCKPAGE, $READBASELIMIT, $READSPT,$UNLOCKPAGE, and $WRITEPTE◦ Functions and procedures that are changed: $AXADR: Replace with standard interface $FREEZE: Replace with the $TRIGGER function. $HALT: Replace with the $TRIGGER function. $STACK_ALLOCATE: Perform different rounding and alignment. Address of allocated area aligned to 16-byte boundary Size of allocated area rounded up to the multiple of 16 bytes5 - Application Migration 13
    • 14. Other pTAL Migration TasksOther pTAL Migration Tasks◦ Procedure attributes TNS/E pTAL does not support the INTERRUPTprocedure attribute◦ 16-byte-aligned data The TNS/E pTAL compiler providesSTRUCTALIGN (MAXALIGN) attribute.Thisattribute causes data to be aligned on the maximumalignment defined for the platform, which is 16bytes for TNS/E platform.5 - Application Migration 14
    • 15. Other pTAL Migration TasksOther pTAL Migration Tasks◦ FIELDALIGN directive in mixed languageprogramming FIELDALIGN (PLATFORM) causes the pTAL compiler to usethe same data alignment as other compilers on the sameplatform FIELDALIGN (AUTO) allows the pTAL compiler to determinedata alignment based on what is most efficient◦ Functions that return condition code and value: TNS/E pTAL compiler issues warning Not callable from C/C++ TNS/R pTAL 64-bit workaround no longer works Write jacket procedure in pTAL5 - Application Migration 15
    • 16. TNS/E Native C/C++ CompilersTNS/E Native C/C++ Compilers◦ TNS/R and TNS/E native C/C++ compilersconform to the ISO/ANSI C languagestandard Programs migrating from TNS/R most likely requireno changes unless they depend on the underlyingmachine architecture or use undocumentedfeatures (mainly privileged features)◦ C/C++ main routine object file name In Guardian: CCPLMAIN In OSS: cpplmain.o5 - Application Migration 16
    • 17. Standard C++ Run-Time LibrariesStandard C++ Run-Time Libraries◦ Three versions of the standard C++ library areavailable on NonStop systems: VERSION1 Data structures and algorithm libraries string, complex, and numeric_limits classes Not supported on Integrity NonStop systems Tools.h++ version 6.1 library VERSION2 STL (Standard Template Library) Memory management, language support, locale and exception handlingfeatures Tools.h++ version 7 library VERSION3 Conforms to ISO/IEC IS 14882:1998 (E) standard for C++ Does not support any version ofTools.h++ library5 - Application Migration 17
    • 18. Native C/C++ Library MigrationNative C/C++ Library Migration◦ Native C run-time library Native C run-time library on S-series and on IntegrityNonStop are nearly identical◦ Native C++ run-time library Migrating from C++VERSION2 andVERSION3 on S-seriesto the respective version on Integrity NonStop shouldrequire no additional source code changes Migrating from C++VERSION1 on G-series to C++VERSION2 on Integrity NonStop requires source codechanges If linking the program as a separate step, you must also specify theZCPPCDLL and ZCPP2DLL on the eld command Tools.h++ version 6.1, if any, should be migrated toTools.h++ version 7 Recommendation is to migrate toVERSION35 - Application Migration 18
    • 19. Native C/C++ Library MigrationNative C/C++ Library Migration◦ Native C++ run-time library (Continued) Migrating from C++VERSION1 on S-series to C++VERSION3 on Integrity NonStop requires source codechanges The two versions are source code compatible; the only differences arein the names of header files Requires source code changes to remove any use ofTools.h++ library Migrating from C++VERSION2 on S-series to C++VERSION3 on Integrity NonStop requires source codechanges It is recommended that you convert to C++VERSION3 onS-series, then to C++VERSION3 on Integrity NonStop Requires source code changes to remove any use ofTools.h++ library5 - Application Migration 19
    • 20. Changed Pragmas and FlagsChanged Pragmas and Flags◦ The following pragmas and flags are either obsoleteor have different behavior: EXTERN_DATA GP_OK allows GP-relative addressing forexternal data references.This pragma is ignored and awarning is issued in TNS/E systems. NON_SHARED pragma is ignored and a warning is issued SRL pragmas or –Wsrl flag is ignored and a warning is issued SRLExports or –Wsrlexports is ignored and a warning isissued SRLExportMembers or –Wsrlexportmembers is ignoredand a warning is issued SRLName or –Wsrlname is ignored and a warning is issued5 - Application Migration 20
    • 21. Changed Pragmas and FlagsChanged Pragmas and Flags◦ The following pragmas and flags are either obsoleteor have different behavior (Continued): INSPECT Controls the selection of the debugging tools.The order ofprecedence follows: For S-series non-PIC:Visual Inspect, Inspect, DEBUG For S-series PIC:Visual Inspect, DEBUG For Integrity NonStop:Visual Inspect, Native Inspect NOINSPECT Controls the selection of the debugging tools.The order ofprecedence follows: For S-series: DEBUG For Integrity NonStop: Native Inspect5 - Application Migration 21
    • 22. Changed Pragmas and FlagsChanged Pragmas and Flags◦ The following pragmas and flags are either obsoleteor have different behavior (Continued): NLD or –Wnld is replaced with ELD or –Weldrespectively LD or –Wld is replaced with ELD or –Weld respectively VERSION1 replaced withVERSION2 orVERSION3 –Wversion1 replaced with –Wversion2 or –Wversion35 - Application Migration 22
    • 23. Neutral C++ DialectNeutral C++ Dialect◦ The neutral C++ dialect consists of librarycomponents that are sharable betweenVERSION2andVERSION3 of the C++ standard libraries◦ Permits middleware to supportVERSION2 andVERSION3 clients◦ Two pragmas are provided in support of the neutralC++ dialect: NEUTRAL: Marks a class definition as being sharable (allowed only instandard header files) BUILD_NEUTRAL_LIBRARY: Used to create DLLs that use theneutral dialect. If this pragma is specified and the program referencesan object not marked with NEUTRAL, a compiler error is issued.5 - Application Migration 23
    • 24. Other C/C++ MigrationTasksOther C/C++ MigrationTasks◦ New C and C++ features Pragmas NEUTRAL: Marks an object as sharable betweenVERSION2andVERSION3 of the C++ standard library BUILD_NEUTRAL_LIBRARY: Build a DLL using the neutralC++ dialect MAXALIGN:Aligns composite objects to the16-bytealignment, which is the maximum alignment supported bythe compiler for some functions to work. Most programswill not need to declare the MAXALIGN pragma, as it isincluded in the standard header file that supplies the datatype declaration.5 - Application Migration 24
    • 25. Other C/C++ MigrationTasksOther C/C++ MigrationTasks◦ New C and C++ features (Continued) New 64-bit unsigned integer data type Type declaration is unsigned long long New functions for conversion between characterstrings and the 64-bit integer type: strtoll — Converts a character string to asigned long long integer strtoull — Converts a character string to anunsigned long long integer wcstoll — Converts a wide-character string to asigned long long integer wcstoull — Converts a wide-character string to anunsigned long long integer5 - Application Migration 25
    • 26. Other C/C++ MigrationTasksOther C/C++ MigrationTasks◦ Data type for 32-bit values in CEXTDECS filechanges from long to int When recompiling native TNS/R programs for the TNS/Eenvironment, if The parameter is passed by value: automatic type conversion is doneand no warning is issued The parameter is passed by reference: correct code is generated andthe warning of mismatched data types is issued One of the following actions may be taken, but is notrequired: Use theWARN/NOWARN pragma or flag to suppress the warningmessage Use the int type instead of the long type in the calling program Use __int32_t typedef for 32-bit items5 - Application Migration 26
    • 27. Other C/C++ MigrationTasksOther C/C++ MigrationTasks◦ TNS/R and TNS/E systems use opposite conventionsfor returning quiet and signaling NaN (not-a-number)values◦ Programs that depend on the TNS floating pointformat must specify the TANDEM_FLOAT pragmabecause the default floating-point format is IEEE◦ Replace _TNS_R_TARGET feature test macro with_TNS_E_TARGET◦ Use _TANDEM_ARCH_ feature test macro toidentify the platform 0 for TNS, 1 for TNS/R and 2 for TNS/E5 - Application Migration 27
    • 28. TNS/E Native COBOL CompilerTNS/E Native COBOL Compiler◦ Supports the same functions and features asthe TNS/R native COBOL compiler◦ Compiles most TNS/R native COBOLprograms and executes them correctly◦ Any program called by a migrated applicationmust also be migrated to TNS/E native mode◦ All code produced by the compiler is PIC5 - Application Migration 28
    • 29. COBOL Compiler DirectivesCOBOL Compiler Directives◦ The following obsolete compiler directivescause a warning to be issued if they are notremoved. No code change is required. NON-SHARED: In a TNS/E system, all code issharable PIC; therefore, this directive is ignored LARGEDATA: In a TNS/E system, there is nodistinction of data areas so this directive is ignored LESS-CODE: In a TNS/E system, native COBOLdoes not support the option to use a system call toinitialize the Extended-Storage Section and thisdirective has no effect5 - Application Migration 29
    • 30. COBOL Compiler DirectivesCOBOL Compiler Directives◦ The following compiler directives have differentmeanings and changes may be required UL: Has the same effect as the SHARED directive. If used withCALL-SHARED or SHARED, can cause an error. If used withRUNNABLE, causes the compiler to link the object file into a DLL. SEARCH and CONSULT:These must specify TNS/E object files OPTIMIZE: 0 no optimization 1 produces optimization for use with debugging 2 produces full optimization INSPECT: If available, selectsVisual Inspect over NativeInspect as the debugging tool NOINSPECT:Selects Native Inspect as the debugging tool5 - Application Migration 30
    • 31. Other COBOL Migration TasksOther COBOL Migration Tasks◦ Use of floating-point data TNS/E native COBOL uses the IEEE format, not HPproprietary TNS format◦ Alignment of Level-01 and Level-77 data items are aligned on an 8-byte boundary can be aligned on an 4-byte boundary by adding theSYNCHRONIZED clause to the declarations◦ File names referenced in the following contexts arechanged from NMCOBEX<n> to ECOBEX<n>where <n> is 0, 1 or T: CONSULT, LIBRARY, and SEARCH directives File-mnemonic clause of the SPECIAL-NAMES paragraph OF or IN clause of the CALL or ENTER statement5 - Application Migration 31
    • 32. User Library MigrationTasksUser Library MigrationTasks◦ The user library is an object file that the operatingsystem links to a program file at run time◦ TNS/R native user libraries: Non-PIC user library is a special form of shared run-timelibrary (SRL) PIC user library is a dynamic-link library (DLL)◦ TNS/E supports PIC user libraries only◦ Migrating either type of TNS/R native user libraryrequires recompiling and relinking5 - Application Migration 32
    • 33. User Library MigrationTasksUser Library MigrationTasks◦ Migrating SRL-type of TNS/R native user library For pTAL programs Guardian environment: Use EPTAL with CALL_SHARED directiveon the command line PC: Use eptal with –shared flag on the command line For C/C++ programs Guardian environment: Use CCOMP or CPPCOMP OSS environment or PC: Use c89 with –Wshared flag. Replace SRLwith SHARED pragma For COBOL programs Guardian environment: Use ECOBOL with SHARED, ELD, andRUNNABLE directives on the command line(or in the source code) OSS environment or PC: Use ecobol5 - Application Migration 33
    • 34. User Library MigrationTasksUser Library MigrationTasks◦ Migrating DLL-type of TNS/R native userlibrary For all programs DLLs on TNS/E systems are functionally identical to DLLson TNS/R systems Recompile DLLs with TNS/E native compiler and link theobject codes with TNS/E eld linker using same compilerdirectives and same linker flags5 - Application Migration 34
    • 35. Floating-point Consistency ChecksFloating-point Consistency Checks◦ Possible linkfile and loadfile floattype settings: TANDEM_FLOAT IEEE_FLOAT NEUTRAL_FLOAT◦ Set by compiler or eld◦ Checks performed: Link-time TANDEM_FORMAT and IEEE_FORMAT can not be linked together Override by setting floattype explicitly using eld Run-time Program file and Ordinary DLL must match or one be neutral Override by setting float_lib_overrule using eld5 - Application Migration 35
    • 36. Guardian API Migration TasksGuardian API Migration Tasks◦ Procedures having different behavior Different buffer alignment for GETPOOL andPOOL_GETSPACE_ procedures ForTNS/R native callers, the above procedures return pointers to4-byte aligned buffers. ForTNS/E native callers, the above procedures return pointers to16-byte aligned buffers by default Results may differ when the pool is already near capacity. It maynot be possible to allocate as many data blocks on aTNS/E systemas on aTNS/R system DEBUG and PROCESS_DEBUG_ procedure invokes H-series debuggers Visual Inspect, Native Inspect, or Inspect5 - Application Migration 36
    • 37. Guardian API Migration TasksGuardian API Migration Tasks◦ Procedures having new return values PROCESSORTYPE procedure returns: 10 indicating an EPIC processor PROCESSOR_GETNAME_ procedure returns: For name parameter: NSE-A For cpu-type-out parameter: 10 For cpu-model-out parameter: 1 to 92* PROCESSOR_GETINFOLIST_ procedure returns: For processor type: 10 For processor model number : 1 to 92* For processor name: NSE-x For processor full name: HP NonStop System EPIC Model x CPU Number of IPUs for NSMA TOSVERSION and REMOTETOSVERSION proceduresreturn the value of R065 - Application Migration 37
    • 38. Guardian API Migration TasksGuardian API Migration Tasks◦ Superseded procedures The DELAY procedure is deprecated; it is supercededby the PROCESS_DELAY_ procedure◦ New procedures to support processmanagement enhancements PROCESS_DELAY_ TIMER_START_ TIMER_STOP_ TS_NANOSECS_ TS_UNIQUE_COMPARE_ TS_UNIQUE_CONVERT_TO_JULIAN_ TS_UNIQUE_CREATE_5 - Application Migration 38
    • 39. Third-Party ToolsThird-Party ToolsEnsure that any third-party tools you useare available for TNS/E systems:◦ Development tools◦ Code libraries◦ Operations tools Schedulers Performance monitors Backups5 - Application Migration 39
    • 40. Data Dictionary MigrationData Dictionary MigrationNew DDL Compiler on TNS/E◦ ?DICTThis dictionary was created by a differentversion of the DDL compiler. It can be read butnot updated by this DDL compiler.To convert your dictionary: ?DDL TEMP OUTPUT * ?NODDL, DICT! ,COMMMENTS, SOURCE TEMP5 - Application Migration 40
    • 41. Questions ?Questions ?41
    • 42. 5 - Application Migration 42