|
|
|
||
|
|
May 2006 |
||
|
|
eDeveloper for iSeries ISAM Client Version 9.4 SP7 – 0.5 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We are proud to present the eDeveloper for
iSeries ISAM Client for eDeveloper Version 9.4 SP7. The eDeveloper for iSeries ISAM Client
V9.4 SP7– 0.5 modules provided in this service pack update the previous
iSeries ISAM Client files. Double-byte character set (DBCS) version iSeries 5250 Emulation Component (MAGIC5250) eDeveloper 9.4 Sample Package for iSeries Component for Accessing iSeries System
Services General
Information (Top) The eDeveloper for iSeries ISAM Client Version V9.4 SP7– 0.5 lets you access DB2/400 data files and OS/400 functions such as CL/RPG/COBOL programs, CL commands, Data Area, and other iSeries objects. Supplied Modules (Top) Main Product – This iSeries ISAM Client version provides the
MGEAC32.DLL file that allows access to the DB2/400 data files and OS/400
programs and commands. Host Library – This iSeries ISAM Client version provides an
updated iSeries host library. Middleware – This iSeries ISAM Client version provides support
for the EAC32TCP.DLL and EASY32MG.DLL TCP/IP communication protocols. Languages – This iSeries ISAM Client version provides ASCII
to EBCDIC conversion files for English, French, German, Polish, Spanish, and
Hebrew. Thai and Italian conversion files are located in the Thai and Italian
support directories. Documentation – The iSeries Guide,
How to Deploy Magic Applications in an iSeries Environment, Magic
eDeveloper V9 is included in PDF
format.
iSeries License Registration (Top) The MSE Operations department provides
iSeries License PAK information in both PDF and text file format. You can copy the
information from the PDF file to enter the information manually on either the
Windows or the iSeries platform, or you can download the text file to your
Windows machine to enter the information automatically. You can enter your License PAK information
manually or automatically on the Windows platform. To enter your license
information on the Windows platform, click iSeries License Registration in
the eDeveloper product group on the Windows Startup menu to open the iSeries
License Registration screen: ·
To enter the
information automatically, specify the location of the PAK text file you
received from MSE under Select License Source, and click Execute. ·
To enter the
information manually, select Manual, enter the information in the enabled fields,
and click Execute. You can also enter the information
manually on the iSeries platform using the EASYCLEF command. Note: If you have already installed eDeveloper iSeries products for
version 9.4, your current license is no longer valid for version 9.4 SP4.
Contact your local Magic office to get a new license. Double-byte character set (DBCS) version (Top) The installation of the iSeries DBCS
client results in the following: ·
The LOCPATH
environment variable is set to the eDeveloper directory ·
The DBCS specific
configuration file contains the parameters listed below: o
DBCS=IBM-950:IBM-937
for Traditional Chinese o
DBCS=IBM-1381:IBM-935
for Simplified Chinese o
DBCS=IBM-949:IBM-933
for Korean. iSeries 5250 Emulation
Component (MAGIC5250) (Top) This component lets you run Telnet
emulation for iSeries from the eDeveloper client. You can download this
component from the Magic Component site http://components.magicsoftware.com/ eDeveloper
9.4 Sample Package for iSeries (Top) This sample provides an application that
demonstrates how you can use eDeveloper for iSeries new features in an
eDeveloper-based Windows application.
You can download the updated Samples package from our FTP site using
the following link: http://v9product:PrEver983@ftp.magicsoftware.com/v9product/94samples/iSeriesSamples/ eDeveloper lets
you connect to iSeries without entering an OS/400 user profile and password.
By using Single Sign-on, you can sign on once to a network server and
automatically gain access to iSeries from your eDeveloper program. iSeries Program Call Wizard (Top) This wizard,
available from the Tools Menu, lets you generate an eDeveloper program that
can call an existing Native iSeries program. Note: if
you are updating an existing eDeveloper version, you must copy a text from
the "To be added to Magic.ini.txt" file located in the iSeries_Utilities/Program_Call_Wizard
directory and paste it under the TOOLS_MENU section in the Magic.ini
configuration file Component for accessing iSeries System Services (Top) The Functions component, located in the Functions directory under iSeries_Utilities folder, lets you access iSeries system services such as spooled file entries, IFS directory objects and iSeries system values, from an eDeveloper application. For more information, refer to the component Readme file located in Functions directory. To access this component you must have the MAGIC400 Host Library, provided by eDeveloper V9.4 SP4, installed on your iSeries machine. You must add the component file, function.mci, located in the Functions directory to your eDeveloper application, and add a database entry for the QTEMP library in the eDeveloper Database repository. Note:
the component programs are also available in the export format in the Functions
directory This option, available from the eDeveloper program menu, includes Legacy Connector and Magic Navigator applications. Legacy Connector application enables any Magic eDeveloper programmer to quickly and easily integrate iSeries (5250) terminal interfaced application with eDeveloper's Windows/Web applications. Magic Navigator is out-of-the-box application, which can be used immediately by iSeries system administrators and operators to access system services including Active Jobs, Spooled File, IFS Objects, and System Values. In addition, the Magic Navigator enables system administrators to send email, execute a CL command, and check the system status, including memory and disk usage. The customer-reported QCR that was fixed
in the iSeries ISAM Client Version 9.4 SP7 is: QCR# 2483 – StartSession
UDF/UDP did not reconnect to iSeries after executing the EndSession UDF/UDP. |
|
|
|
|
Thank you, Magic iSeries Team |
|
|
|
|
|
|
|
|
|
|
|
|