Skip to content

Pre-Requisites

Operating System

IBM i (AS/400) System with OS/400 Release V7R2M0 or higher

The current version can be checked using command WRKLICINF

PTFs

  • Latest cumulative PTF's for TCPIP/IP
  • Latest cumulative PTF's for IBM HTTP Server for i

MRLICKEY License key command

In order to use the products, a valid License Key is required for the core product MDRest4i, which is based on the Serial Number of the system, and the version of the Product.

MDREST4i uses a license key system independent from MDCMS. So anylicense keys or installations for MDREST4i prior to May 21, 2020 will need to be reentered into MDRST4i using prompted command MDRST/MRLICKEY LTYP(\*INT) after the new version is installed.

Please provide Midrange Dynamics or a reseller with the serial number (obtained with command WRKLICINF or DSPSYSVAL QSRLNBR) and product version and continue with the installation once the key or keys have been provided.

The following screen will appear when using MDRST/MRLICKEY LTYP(\*INT):

                         Modify MDRest4i License Keys                


Enter the new License Key(s) and press Enter.                        

 Product       License Key          Status                           
 MDRest4i      ____ ____ ____ ____

                           System Serial Number: 78656EX             
                                     Partition#: 007                 
                                     Version ID: 14                  

F3=Exit

Paste in the key provided in the email received from Midrange Dynamics support, and press enter

If the keys are provided in file MDLICENSE.savf, include this file in the same IFS path or library as the product save files. When MDLICENSE.savf is included, the keys for the given serial number will be automatically applied to the product instance, and the keys for all other included systems will be stored in the product instance so that if a switch is made to a backup system, the backup keys will automatically be applied to the product, thus avoiding any delays.

Note: License keys obtained as a save file (SAVF) from the mdlicense.mdcms.ch website will sometimes have additional data in the save file name. for example: “MDLICENSE_20220829_160955_411724.savf” Before running MRLICKEY to install this save file, rename it so the name of the save file is “MDLICENSE.savf”

User Authorization

The user performing the installation must have *SECADM and *ALLOBJ authority on the system.

Access to the Digital Certificate Manager (DCM) is required for using SSL for REST APIs or Consumers and SOAP Services or Consumers

Adopted Authority

The system value QALWOBJRST must include the choice of *ALL or *ALWPGMADP so that the product programs with the adopt attribute can be restored.

Disk Space

The product initially requires about 205 MB of space at installation time.

MDREST4i history typically requires an additional 5 MB per year of use. This is subject to the logging details selected in each program generated.

Product Library Locks when Upgrading

When upgrading an existing version of the MD Products to a new build, the existing library instances for MDRST, may not be in use.

Object locks can be checked by using command:

WRKOBJLCK OBJ(MDRSTxxxx) OBJTYPE(*LIB).

Where “xxx” is the instance extension – blank if the default MDRST was used.

Please also check any http instances that use MDRST instance libraries in the ScriptAlias, ScriptAliasMatch, SetEnv QIBM_CGI_LIBRARY_LIST or job descriptions ( mdrst/mdrst) setting in the HTTP server instance configuration. These server instances should be stopped until after the installation.

If locks exist, you can cleanly end the jobs ahead of time, or specify parameter END(*YES) on the MDREST4INS command to automatically end all jobs locking the product libraries.