Communication errors:

TCP/IP DDM Server    

Some features of TMA Graphics/400™ applications utilize the AS/400 TCP/IP DDM server.  This server job must be installed and running on your system.  Prior to V4R2, PTF’s are required to activate this feature (see table below):

On Pre-R420 systems, CALL PGM(QSYS/QCNSKSVR) to start the target DDM job QCNSKSVT.  To verify if active, WRKCFGSTS *CTL QCNSKSVR

On R420 and later systems, STRTCPSVR *DDM (or *ALL) to start the DDM server.  To verify if active, run NETSTAT  *CNN and verify that locatl port drda (port 446) is in Listen mode.  You should also run WRKSBSJOB SBS(QSYSWRK) and verify that jobs QRWTLSTN and QRWTSRVR are active.

 For more information, please visit IBM’s technical knowledgebase and search for Reference Number 862565C2007C9F3D

http://www-1.ibm.com/support/manager.wss?rs=0&rt=0&org=as400&doc=B5F0B7784346EDB6862565C2007C9F3D

MDAC (Microsoft Data Access Components)     Return to Top

A key component of TMA Graphics/400™ is MDAC.  This Microsoft strategy provides high-performance access to all types of information across an organization, from desktop to enterprise systems.  Microsoft released the first version of MDAC in 1996.  Since then, more technologies have been added and several version releases have been issued to enhance the product capabilities.  The earliest version, MDAC 1.0 was first released with Windows 95.  Version 2.7 is now available.  Upgrades of MDAC have appeared in each release of Windows as well as in other Microsoft products including Internet Explorer, SQL, Visual Basic, and Microsoft Office. 

 TMA Graphics/400™ requires MDAC 2.5 or higher.  During installation, the Microsoft Software Installer (MSI) will check your PC for MDAC compatibility and automatically install MDAC 2.5 if your system is running an older version.  If this update occurs, your will be prompted to reboot your PC for the application installation to continue. 

 For more information, please visit Microsoft’s Universal Data Access site.

Client Access and Service Packs  Return to Top

A key component of MDAC utilized by Graphics/400™ is ADO (Active Data Objects).  The minimum level of ADO support is V2.5.

 IBM began support for ADO with Client Access for Windows 95/NT V3R1M3, however the earliest versions for Client Access required upgrades via service packs to support more recent versions of ADO.  The chart below shows the various versions of Client Access and Client Access Express and the required service packs for ADO 2.5 support and higher.

 During the installation of Graphics/400 applications, an ADO/Client Access validation program will run immediately after the README dialog box.  You version and service pack level of Client Access will be tested for compatibility to ADO2.5.  If the validation test fails, you may continue with the installation, but will not be able to run the application until Client Access has been upgraded.

 For more information, please visit IBM’s technical knowledgebase and search for APAR II11872

http://www-912.ibm.com/n_dir/nas4apar.nsf/51d11a683a56a5cc862564c000763b23/428f9997d1744f1c8625677f003283c9?OpenDocument

Installation errors:

Error 1931 - MSADO is protected by Windows…   Return to Top

This message is informational only.  It appears because the windows installer has detected a more recent version of MS-Active Data Objects on your system.  No action is necessary!  Select OK to continue with the installation.

PRMS Environment:   Return to Top

Each Graphics/400™ application has a PREFERENCES menu where you must define your company-specific setup of the PRMS application environment.  The information needed for each application varies, but the types of information are database libraries, files, file members, and company numbers.  If this information is unknown by you and you do not have access to your company’s MIS Technical support staff, it can be derived from active PRMS jobs. 

             PRMS Company Number     Return to Top

Some Graphics/400™ applications may prompt you for the PRMS company number.  You can locate the company number by signing-on to a PRMS menu.  The company number will appear in the top-left corner of each PRMS menu, just to the right of the menu name.  The company number must be between 1 and 999.  If your PRMS environment is setup for Multi-plant, you will see two numbers in the top of the menu.  The first number is the company number and the second number is the plant number.

            PRMS Database Library     Return to Top

The database library holds the PRMS files.  On a PC, an AS/400 library would be similar to a folder.  To reference a file, you must know the library it is stored in.  Here are two options for determining your PRMS database library.

RMS Database Data Area – A data area stores very specific information.  PRMS uses a data area to store the name of its database library.

1.      Sign-on to a PRMS environment

2.      Press F3 or F10 to exit the menu to a command line prompt.  If you have been restricted from this feature, see the DSPJOB option.

3.      Type in the command DSPDTAARA RMSDBLIB and press ENTER

4.      The PRMS database library name will be displayed

DSPJOB (Display Job) – An AS/400 command that shows information about the active job.

1.      Sign-on to a PRMS environment

2.      Choose a common inquiry option, i.e., IN0008-Product Inquiry

3.      Activate the System Request prompt by simultaneously pressing <ALT>/<ESC> keys

4.      A prompt will appear on the bottom on your screen.  It the first position, type 3 and press ENTER

5.      The DSPJOB menu will appear.

6.      Type option 14 (Display Open Files) to list all files used by the active job

7.      The first three columns are FILE, LIBRARY, and MEMBER

8.      Some files are system files, some belong to menu master, and some are database files used by the application

9.      Database application files use a unique naming convention, AANNT999 where AA is the application initials, i.e., IN=Inventory, MS=Multi-System, AP=Accounts Payable, etc.  NN is a very abbreviated file name, i.e., PM=Product Master, WI = Warehouse Inventory, WC = World Control.  T is the file type, i.e., P=Physical, L=Logical, and J=Join.  999 is the file number, generally between 100 and 500.

10.  Once you identify a database application file, read across to determine the database Library name.  Generally, you will see multiple database application files all in the same database library name.

             PRMS Files     Return to Top

Each Graphics/400™ application will require a reference to one or more PRMS files.  The file names are provided as defaults in the application.  They also appear in the input text box tool-tip notes and in the application documentation.  Generally, the default names are all that is required.  In rare cases, your in-house technical staff may have renamed the files.  This is not likely, but possible.  If you experience any communication errors, have your MIS staff verify the file names.

             PRMS File Members     Return to Top

All PRMS files have at least one file member.  A file member is AS/400’s way of defining file subsets.  PRMS typically uses file members in a multi-plant environment to distinguish a corporate database and each plant’s database.  There is a direct correlation between the PRMS Company number and the file member name.  Standard naming conventions in PRMS append an “M” to the 3-digit company number, i.e., company number 25 is member M025 and company number 100 is member M100.  The file member names can be verified by using the DSPJOB command described above.

    Single Member vs. Logical Members     Return to Top

PRMS environments that use multiple file members are not compatible with some AS/400 commands required and used by Graphics400™ applications.  To work around this issue, you may need a special type of file that presents a multiple member file as a single member file.  These files are generally known as “single-member logical file”.  Since these file types are not unique to Graphics/400™ but also to many other PC and AS/400 applications, you may already have these files defined on your system.  If not, you will be required to create them or have them created for you. 

 A programmer can create these files with the command CRTLF (Create Logical File).  If you do not have authority and expertise in this area, or access to someone who does, TMA provides a free utility program that will create the files for you.  This utility can be downloaded from our website or installed from the application CD.  The application includes on-line help to guide you through the process.

Return to Top 

Home | Products | Services | News | About_Us | F.A.Q. | VideoTraining

Questions or problems regarding this web site should be directed to [CompanyEmail].
Copyright © 2002 [CompanyName]. All rights reserved.
Last modified: 05/26/08.