Tmax 5 SP2 Fix#1

This chapter briefly describes newly added and changed features in Tmax 5 SP2 Fix #1. For detailed information, refer to the relevant guide.

1. Added features

This section describes the major features added.

1.1. Engine

  • Added the ability to process file logins in tmm in a different thread.

    • Add [-g] / [-m] options to TMMOPT section

      Item Description

      [ -g ]

      Create a separate thread for file writing and process it. If not set, it will be processed in the main thread as before.

      [ -m ]

      Specifies the number of requests to keep when file writes are slow. If not specified, it is fixed at 10,000. Each request consumes approximately 8,192 bytes.

      This setting is meaningful only when used with the [-g] option.

    • Related issue: IMS 77057

  • Added the ability to output TPENOENT errors to SLOG

    • In versions prior to Tmax 5 SP3, TPENOENT errors, which occurred due to operational issues, could only be detected on the client. If these errors were recorded in the SLOG, system operators could quickly identify the cause of the error without having to check the client. This version adds a feature that records TPENOENT errors in the SLOG.

    • CLHOPT = " -x 1"

      • If not set, it will not be recorded in SLOG.

    • Related issue: IMS 47663

1.2. Tuxedo Gateway

  • Added the Tuxedo Gateway TIMEOUT option

  • Added the COUSIN IRT functionality to Tuxedo Gateway

    • A feature has been added to allow normal scheduling even in case of channel failure when the Tuxedo gateway is set to COUSIN.

    • CLOPT: [ -l ] setting is required to use this feature.

    • Related issue: IMS 75505

1.3. Domain Gateway

  • Added a user logging functionality when calling through a domain gateway.

    • Added the ability to log message processing before and after a domain gateway request. Logs are logged for requests/transmissions from clh and requests/transmissions from remote gateways.

    • You can select the type of message to be output through [-p <file path>] in the CLOPT setting of the GATEWAY section.

    • Related issue: IMS 73152

1.4. JEUS_ASYNC GATEWAY

  • Added the failback feature

    • A UCS server can only process one channel at a time. Configuring multiple channels to transmit from CLH to UCS only results in data being queued on the socket, wasting channels. A feature has been added to allow separate INBOUNDCPC configuration for UCS types.

    • Related issue: IMS 77228

1.5. TCP GATEWAY

  • Added a function to turn on/off the output log of the tcpgw session connection termination.

    • When the [-l] option is given to the CLOPT entry, a function has been added to prevent login SVR0030, SVR6102, and SVR6103 from remaining when disconnecting.

    • Related issue: IMS 76422

1.6. Utility

  • Added the fdlc decompile option

    • Added an fdlc option to convert fdl files to text files.

    • Example

      $ fdlc -f tmax.fdl -r de_fdl.f
FDLC is successfully done. total 149 field(s).

    • Related issue: IMS 75051

  • Added the tmd quote handling option

    • Added an option to handle string type data containing " in tmd.

    • If you run tmd -i input file with the -q option, \" in the string data will be recognized as " and processed.

    • Example

      $ tmd -i aa -q
output: ABC "DEF"
$ cat aa
*tpcall TOUPPER STRING
abc \"def\"

    • Related issue: IMS 76132

  • Added the -i option to tmboot

    • When running with tmboot -g, the entire process will stop if a server reaches the max while booting servers. When used with "tmboot -g -i", the entire process will not stop even if a server reaches the max, and the next server will be started.

    • Example

      $ tmboot -i -g svg1

    • Related issue: IMS 72610

  • Added the racdr function

    • In the existing version, it is possible to execute commands (such as tmboot) using racd in the same domain.

      In Tmax 5 SP2 Fix#1, the racdr utility was added to enable command execution or file transfer functions in other domains.

    • How to use

      There are no user changes in racd, and racdr supports the following options:

      racdr [-h][-f cfg_file][-n node_name][-c command]
      [-s file_name][-d dest_no]
      Option Description

      [-h]

      Prints the Usage screen.

      [-f cfg_file]

      Specifies an configuration file that stores node information for other domains. If not specified, the racdr.cfg file in the current directory or the $TMAXDIR/config/racdr.cfg file is used.

      [-n node_name]

      Specifies the node name defined in the configuration file. All requests are forwarded to and processed by the racd of the corresponding node.

      [-c command]

      Executes a command in racd. If the command has parameters, they must be enclosed in quotes and passed as a single argument.

      Only tmboot, tmdown, cfl, and gst commands are allowed. Other commands or shell scripts cannot be executed.

      [-s file_name]

      Transfers a file to the node. Must be used with the -d option.

      If a file already exists in the destination location, the file’s name will be changed and the transferred file will be saved with the original file name. The existing file’s name will have the current "_year, month, day, hour, minute, second" appended to it. If a file with the same name already exists, "_number" will be appended to it.

      If a file transfer fails, the file being transferred is deleted and the existing file is restored.

      [-d dest_no]

      Specifies the path where the file will be saved.

      Up to three paths can be specified. The paths are set in the configuration file, and dest_no specifies the number of the set directory.

      The first path (dest1) specifies 1, the second path (dest2) specifies 2, and the third path (dest3) specifies 3.

    • How to set up the racdr configuration file

      The configuration file is set in the following format:

        -----------------------------------------------------------------------
  #nodename  ip-address    racport  dest1(appbin)  dest2(applib)  dest3(config)
  tmnode1    192.168.1.1   5000     /tmax/appbin   /tmax/applib   /tmax/etc
  tmnode2    192.168.1.2   5000     /tmax/appbin   /tmax/applib   /tmax/config
  othnode    192.168.10.2  9999     /tmax/appbin   /tmax/applib   /tmax/config

    • Caution

      • When executing a command, you must set the -n option in the command argument parameters to execute only the corresponding node.

      • Commands that require input cannot be processed. The command arguments must be set to perform in a way that does not require input.

        $ tmdown
       Do you really want to down whole Tmax? (y : n):
        $ tmdown -n node1

      • The execution screen results are sent to the client when the command has completed all executions and exited.

      • The STDOUT and STDERR outputs in the execution screen results may be output in a different order than the actual screen.

      • The STDERR contents of tmboot are not printed in the racdr execution results.

      • While the command is running, racd cannot process other requests.

    • racd usage examples

        $ racd
  $ racd -k

    • racdr usage examples

      The following is an example of transferring the file /app/svr2 to the /tmax/appbin directory on node tmnode1.

      $ racdr -f config.txt -n tmnode1 -s /app/svr2 -d 1

      The following is an example of executing the cfl command on node tmnode1.

      $ racdr -f config.txt -n tmnode1 -c "cfl -i tmaxconfig.m"

      The following is an example of executing the tmboot command on node tmnode1.

      $ racdr -f config.txt -n tmnode1 -c "tmboot -n node1"

      The following is an example of shutting down a specific server on node tmnode1.

      $ racdr -f config.txt -n tmnode1 -c "tmdown -n node1 -S svr2"

    • Related issue: IMS 72610

  • Added the cfl -x option

    • When performing cfl, if the [-x] option of TARGET and CLOPT is used in the SERVER section setting, check whether the server/service name exists.

    • Added error messages

      • When a server name that is not declared in the configuration file is set in the TARGET setting of the SERVER section, the following error message is output.

        CFL3184 line %d(line at which server was declared): invalid target server name %s(server name specified in TARGET)

      • When the -x option is set to a service name that is not declared in the configuration file in the CLOPT setting of the SERVICE section, the following error message is output.

        CFL3183 line %d(line at which server was declared): invalid service name %s(service name set using -x)

    • Related issue: IMS 75628

  • Added the tmd -l option

    • When running the existing tmd, the line receiving data was limited to 1024 bytes. A feature has been added to allow users to set the size to the maximum data size they wish to set.

    • Example

      $ tmd -i test.64000 -l 64003

    • Related issue: IMS 73033

1.7. Management tools

  • Added the st -v -pod function

    • When applying st -v -pod in tmadmin, a function has been added so that "(POD)" is always printed in the status section of the server that is a POD.

    • How to use

       $$3 tmaxs7 (tmadm): st -v -pod
------------------------------------------------------------------------
  clh   svrname    (svri)   status     count   qcount   qpcount  emcount
------------------------------------------------------------------------
    0   _rqsvg     (   2) RDY              0        0         0        0
    0   svr2       (   5) NRDY(POD)        0        0         0        0
    0   svr3       (   6) RDY              0        0         0        0
    0   svr_ucs    (   7) RDY              0        0         0        0
    0   svr_rq     (   8) RDY              0        0         0        0
    0   fdltest    (   9) RDY              0        0         0        0

    • Related issue: IMS 75147

  • Check the maximum number of users who can connect to clh

    • In tmadmin, a function was added to output the following in the tmaxinfo(ti) and cfg -n commands.

    • How to use

      $$1 tmaxs7 (tmadm): ti
         Supported maximum user per node = 12067,
         Supported maximum user per handler = 12067,
$$2 tmaxs7 (tmadm): cfg -n
         Supported maximum user per node = 12067,
         Supported maximum user per handler = 12067,

    • Related issue: IMS 70872

1.8. TDL

  • Option to output the number of collisions when searching by hash collision (I)

    • How to use

      tdlshm -I <mincol>
      Option Description

      [ -I mincol ]

      The value of mincol must be a minimum value greater than or equal to 0, representing the minimum number of comparisons. When outputting each module, information about that module is only displayed if the number of comparisons is greater than or equal to the specified value. Entering a large value allows you to quickly find functions with a large number of comparisons.

2. Changed function

This section describes the major changes to the existing features.

2.1. Engine

  • IPCPERM setting not applied to lockfile

    • When restarting Tmax, the permission is applied according to the IPCPERM setting to the previously created lockfiles (tmmld, clhld00x, tmconfig) in the path directory.

    • Related issue: IMS 78728

2.2. TDL

  • TDL hash function performance improvement

    • To solve the problem of tdlupedate taking a long time when there are many hash collisions, the function was improved to reduce collisions by applying the latest hash function.

    • Related issue: IMS 75196

2.3. Client/Server

  • tpadvertise() / tpunadvertise() function enhancements

    Previously, tpadvertise and tpunadvertise only operated on services registered in the environment settings. This has been improved to allow registration/deregistration of services registered with mksvr and services newly registered by tpadvertise.

    The following describes the changed behavior:

    • svrlib’s tpadvertise

      1. When tpadvertise is performed on a service registered in the environment settings file (config.m)

        • If tpunadvertise was performed, it will be changed to a serviceable state again.

        • If you run tpadvertise on another server, it will fail.

      2. When performing tpadvertise on a service registered with mksvr

        • If tpunadvertise was performed, it will be changed to a serviceable state again.

        • If you run tpadvertise on another server, it will fail.

        • When all server processes are terminated, the services that were tpadvertised are automatically deleted as well.

      3. When performing tpadvertise on a newly registered service by tpadvertise

        • Register a new service.

        • If tpunadvertise was performed, it will be changed to a serviceable state again.

        • Failure when running tpadvertise on another server.

        • When all server processes are terminated, the services that were tpadvertised are automatically deleted as well.

    • svrlib’s tpunadvertise

      1. When performing tpunadvertise on a service registered in the environment settings file (config.m)

        • The state changes to UNADV, and TPENOENT is set in tperrno when calling the service.

      2. When performing tpunadvertise on a service registered with mksvr

        • The state changes to UNADV, and TPENOENT is set in tperrno when calling the service.

        • When all servers are shut down, the service itself disappears. When performing tpunadvertise on a newly registered service by tpadvertise

        • The state changes to UNADV, and TPENOENT is set in tperrno when calling the service.

        • When all servers are shut down, the service itself disappears.

    • Restrictions

      • When running tpadvertise on a service that is not configured, mksvr will act as a process that dynamically registers the service.

      • SVCTIMEOUT and AUTOTRAN cannot be set.

    • Added log

      If tpadvertise has already been performed on another server, it will output the following to slog:

      • SVR3041 fail to tpadvertise: svc(%1) in svr(%2:%3), mysvri(%4)

        (1: service name to tpadvertise, 2: already registered server name, 3: already registered server index, 4: server index on which tpadvertise was executed)

      • TMM3041 fail reg svc (%1, %2, %3, %4) not equal svri(%5)

        (1: Service name to be registered, 2: Service index, 3: Index of already registered server, 4: Index of server group, 5: Index of requested server)

    • Added tperrno for tpadvertise failure

      Error Description

      TPELIMIT

      No new services can be registered due to a limit on the number of services on the node.

      TPEMATCH

      • A service has already been registered but the function is different.

      • The service is already registered on another server.

    • Related issue: IMS 71318

2.4. Utility

  • Removed TIP server MIN/MAX constraints

    • When using the TIP server, the restriction that MIN/MAX could only be set to 1 was lifted, allowing multiple TIP servers to be started.

    • Related issue: IMS 78786

3. Bug Patches

3.1. Engine

  • Fixed the issue where TMM would terminate abnormally during tmdown -i.

    • In a situation where there are many servers restarted due to abnormal termination, and many servers are started by ASQCOUNT, the phenomenon of TMM being abnormally terminated when terminated with tmdown -i has been fixed.

    • Related issue: IMS 75782

  • Fixed the issue where CLH terminates abnormally randomly when performing tpforward on a server and tpreturn on another server.

    • This issue was fixed because it occurred when trying to reference free memory when handling tpreturn for tpforward in CLH.

    • Related issue: IMS 75301

  • Fixed a bug when querying backup gateway information with tmadmin gwi.

    • The issue of TMM abnormally terminating when processing messages sent when querying gateway information from tmadmin to gwinfo has been fixed.

    • Related issue: IMS 75390

  • Fixed an abnormal behavior when calling tpsend on multiple nodes

    • Fixed an error that occurred when calling tpsend after calling tpconnect from a service on the local node to a service on another node.

      (E) CLI 3039 internal error : unknown message type :2006 [CSC5713]

    • Related issue: IMS 77055

  • Fixed the phenomenon of restarting when a process is abnormally terminated during tmdown -s svr.

    • If the server terminates abnormally while shutting down with tmdown -S svrname, TMM restarts it even though it is shutting down and leaves the following error message.

      (E) TMM2108 register request from server(svr2) error: SVR_DOWN_REQUESTED [TMM0156]

      In such situations, the server’s down status has been checked and modified to not restart.

    • Related issue: IMS 70994

  • Fixed CLH memory leak related to the ctx_ereply function

    • Fixed a problem where clh memory leak would not occur when calling UCS services by setting tpacall + TPNOREPLY while ctx_ereply is enabled.

    • Related issue: IMS 75659

  • Fixed an error where statistics on remote nodes were not initialized when restat -a was executed in tmadmin master mode.

    • The issue where, after tmadmin is executed, tmamdin -m is executed on the same node, commands applied to the master, such as restat, in tmadmin -m are not executed on other nodes has been fixed.

    • Related issue: IMS 68751

  • Changed the write retry behavior for other processes in TMM

    • Previously, when TMM tried to continue writing messages sent to tmdown before tmdown read all of them, it was considered a failure if it tried more than a certain number of times (500).

      If a write operation fails, the tmdown process terminates normally on a single node, but on a multi-node system, the tmdown process completes only on the local node and does not execute on the remote side. To resolve this issue, the number of write attempts is increased only after at least 1 second has passed, preventing failure even if many write retries occur simultaneously in a short period of time.

      TMM not_tproc_ready: ind = 2003, fd = 2008, w_trycnt = 500
TMM2084 trying to write to tproc is blocked: tproc (DOWN) closed and data dropped [TMM0022]

    • Related issue: IMS 67087

  • Added description of the -w option to tmboot -h

  • Fixed the abnormal CLH shutdown issue

    • Fixed the issue where clh would terminate abnormally when performing conversation mode with a dynamic server.

    • Related issue: IMS 72946

3.2. Client/Server

  • Fixed the undefined symbols issue in server libraries

    • Fixed the issue where the following symbols were UNDEF in RDP and other server libraries, causing an error when building executables.

      UNDEF  |_tdlend
UNDEF  |_tdlstart
UNDEF  |tdl_version_freezing_no
UNDEF  |tdl_version_freezing_sw

    • Related issue: IMS 78398

  • Modified the server library to not use a variable named current_time

    • When building an AP server, a user library that uses the current_time function was built alongside the server, causing the server to crash when booting and requesting service. This was fixed by renaming the current_time function in the Tmax server library to prevent crashes.

    • Related issue: IMS 77546

  • Fixed the issue where tp_sleep() would not wait when executing the ca command via tmadmin while tp_sleep() was being called on the server.

    • When performing tp_sleep, it was modified to process TMM requests even if there are messages coming from TMM and wait for the remaining time of the timeout.

    • Related issue: IMS 75771

  • Fixed an error that occurred when tx_commiting on the XA server.

    • The phenomenon of an error occurring when tx_commit is performed while operating as xa_end(SUSPEND) due to the logic that checks when calling tpcall(TPNOTRAN) after tx_begin in the XA server has been fixed.

    • Related issue: IMS 75802

  • Fixed the tmm swap memory increase phenomenon

    • When TMAX_TRACE is set, SVCTIME is 1, and the server is under heavy load, the trace log sent to TMM before and after service execution is delayed, resulting in SVCTIMEOUT. The phenomenon of requesting error messages to TMM and mixing messages, preventing TMM from processing properly and increasing swap memory has been fixed.

    • Related issue: IMS 77057

  • Fixed the issue of xid 0-0-0 being issued

    • For some unknown reason, there was a case where xa_start was performed with '0-0-0', which did not have an xid issued, causing a global transaction inconsistency. Therefore, transactions starting with '0-0-0' were responded with a failure, and the caller processed the failure.

    • Output error code

      • "SVR3042 xid is invalid (0-0-0), svc(%s)" is printed, and the service name being called replaces %s.

      • errno is TPETRAN, usrcode is TX_ESYSTEM.

    • Related issue: IMS 77327

  • Fixed the issue where all servers, including those set to MIN by LIFESPAN, would die in the case of the DYN server type.

    • When applying LIFESPAN to the DYN server type, processes with process numbers lower than min are terminated after the IDLE time, and when the entire server is under load and the load is cut off at the same time, the phenomenon of all processes set to MIN being terminated at a certain point has been corrected.

    • Related issue: IMS 79230

  • Fixed the issue where a TRC5003 error occurred when starting UCS.

    • In environments where the engine is 64-bit and the UCS server library is 32-bit, there was an error in the 32-bit library adjusting the shared memory size. This has been corrected so that the 32-bit engine calculates the shared memory size used by the 64-bit engine.

    • Related issue: IMS 75150

  • Fixed the issue where rollback occurred twice when the server was abnormally terminated during 2pc processing.

    • When there are XA servers svr_xa1 and svr_xa2, if svr_xa1 calls tpcall after tx_begin and then terminates svr_xa1 with kill, an issue occurred where xa_rollback was performed with an xid other than the xid that was xa_started. This issue has been fixed when AUTOTRAN is not set for svr or svc.

    • This is a side effect of adding the old version AUTOTRAN compatibility patch function.

    • Related issue: IMS 76716

  • Fixed an error that occurred in TPESYSTEM when using tmax_chk_conn(0) in a multithread client.

  • Fixed the encryption duplication error when tp_strat is used in context in MultiContext

    • When reading environment information with different labels in each context using MultiContext and accessing it, an error occurred after tpstart when encryption was set for some labels. Previously, whether or not encryption was set was not separated for each context, so if encryption was used only for some contexts, a conflict in the settings occurred. In this case, it was modified so that whether or not encryption was set can be set differently for each context.

    • Caution

      Depending on whether encryption is used, encryption must be set in the client configuration file.

      • Unencrypted

        TMAX_SEMANTICS="CRYPT_SW:N"

      • Encryption

        TMAX_SEMANTICS="CRYPT_SW:Y"

    • Related issue: IMS 75976

3.3. Domain Gateway

  • Fixed COUSIN Gateway load balancing errors

    • In the environment below, it was modified to distribute according to the LOAD value in domain B.

      If the environment SVCA of domain A and domain B is set as COUSIN gateway in domain A and COUSIN in domain B

      When SVCA is scheduled through a gateway to the B domain, it has been modified so that it is processed by the receiving node in the B domain regardless of the LOAD value.

    • Related issue: IMS 75689

  • Fixed the issue where TMAX_TRACE was turned ON when the number of gateway requests was 268435456 or more.

    • Fixed the issue where the trace log was output as ULOG when the number of requests exceeded 268435456 after starting on the gateway, even though TMAX_TRACE was not set to ON.

    • Related issue: IMS 77057

3.4. Utility

  • Fixed an error that occurred when performing cfl and the UCS server was set to LIFESPAN=IDLE_DOWN in the configuration file.

    • Fixed the issue where setting LIFESPAN to IDLE_DOWN or DOWN would not cause an error.

    • Related issue: IMS 78830

  • Fixed core occurrence caused by an incorrect value specified for the tmd buffer type.

    • It has been modified to prevent abnormal termination even if the wrong buffer type is set in the data entered by the user.

    • Related issue: IMS 77980

  • Fixed the issue where the TIP server would not start on the node where the gateway was set when configuring a multi-node TIP server.

    • An error occurred while writing an configuration file with cfl, and it has been corrected.

    • Related issue: IMS 71844

3.5. Management Tools

  • Fixed the issue where the -p option of unadv/adv in tmadmin was not applied.

    • Fixed the issue where the -p option of unadv/adv was not applied and no response was received when requesting the unadv -p option.

    • Related issue: IMS 78995

  • Fixed a hang issue that occurred when running tmadmin wsgwinfo

    • Fixed a hang issue when running wsgwinfo when there was no connected WSGW.

    • Related issue: IMS 79458

  • Changed the usage of the ds command from -c clid to -c cli_id.

    • The usage of the ds command has been changed from -c clid to -c cli_id.

    • Related issue: IMS 74424, 79516

  • Fixed an error when the -g and -v options were given simultaneously in tmadmin chtrc and chlog.

    • Fixed an error when running chtrc -g svgname -v svrname -s spec in tmadmin.

    • Related issue: IMS 76320

  • Fixed the issue where the -n option was not applied when searching with st -s.

    • The -n option part was handled incorrectly, so this part has been corrected.

    • Related issue: IMS 72444

  • Fixed the phenomenon of appearing as NDRY when searching with st -s

    • The phenomenon of Tmax server being displayed as NDRY when searching with st -s while the server is down has been corrected.

    • Related issue: IMS 76225

3.6. TDL

  • When a backup is set, shm_backup reflects an incorrect global seqno while running tdlupdate.

    • This phenomenon occurs when the global seqno update point is moved to the end of update while executing tdlupdate. The function has been modified to reflect the global seqno of shm_backup after the global seqno is changed.

    • This phenomenon is an error that occurred in versions after Tmax 5 SP1 r6303 and Tmax 5 SP2 r6400.

    • Related issue: IMS 73527

  • Fixed an error so that getrusage() and gettimeoutday() functions are called only when enabled with MONITOR=Y |tdlshm -s e

3.7. Domain Gateway

  • When trying to connect to a gateway, an error occurs that does not release the socket in certain situations.

    • After adding the non-block connect function reflected in Tmax 5 SP2, the following issues were fixed.

      1. When used without the -i option, a problem occurs where a new socket is created for each request without closing the connected socket.

      2. When using the -i option or using GWCHKINT, a new socket is created without closing the socket if GWCONNECT_TIMEOUT is greater than NLIVEINQ or GWCHKINT.

    • Related issue: IMS 74015

  • Domain GW Failover Not Working

    • Fixed the phenomenon in which the failover of domain GW (TMAX, TMAXNONTX) did not work properly and a TPENOREADY error occurred.

    • Related issue: IMS 77388

3.8. Tuxedo Gateway

  • Fixed the issue where xid could not be found when processing prepare/commit/rollback messages received from CLH in tuxgw.

    • Related error messages

      (E) GATEWAY3020 failed to get xid from txhead [TUXGW0155]
(E) GATEWAY0209 internal error : request table overflow [TUXGW0014]

    • Related issue: IMS 73518

  • Fixed an abnormal termination issue when configuring a multi-node Tuxedo gateway.

    • Fixed a bug that occurred in a multi-node environment where the svgno index accessing shm was using the LOCAL node value as is on the Tuxedo gateway of node 2.

       _flag_eo_control(svrname = "\272\334^O\376\340\335\360^M^O(invalid char ptr (0x0ffffffffffffed0))), line 1508 in "etc.c"
 _eo_control_check(svrname = "", flag = 608715906), line 1600 in "etc.c"
 main.init(argc = 150994943, argv = (nil)), line 414 in "main.c"
 main(argc = 0, argv = (nil)), line 127 in "main.c"

    • Related issue: IMS 77103

  • Fixed the issue of CPU overuse by Tuxedo gateway.

    • Fixed the issue where the CPU (infinite select) usage of the Tuxedo gateway increased when the Tuxedo domain refused the connection while attempting to connect to the Tuxedo domain gateway from the Tmax Tuxedo gateway.

    • Related issue: IMS 78018

3.9. Java Gateway

  • Fixed the issue where jeusgwa would restart infinitely when the specified file did not exist when using the [-a] option in CLOPT of the jeusgw Async Gateway.

  • Added the [-H] option to CLOPT in jeusgw Async Gateway

    • When using [-H], a feature has been added to suppress messages when performing an alive check at log level -D 4.

    • Related issue: IMS 70952

  • Fixed the CDATE macro of CLOPT in jeusgw Async Gateway to reflect date changes immediately

  • Fixed an error that occurred in Core during processing when receiving a field buffer with a field value of type string through the jeusgw Sync Gateway.

    • In jeusgw, an error occurred when converting received fdl data due to not initializing the fdl version value. This has been fixed.

    • Related issue: IMS 75639

  • Fixed the issue where jesugw would terminate abnormally when requesting a string field buffer type service from the jtmax server.

  • Fixed the issue where requests received during an alive check (all requests such as tpcall, tpacall, etc.) would always respond with a failure when making a request to a JEUS type gateway.