The below command currently works even though does not exist in the file system or if it points to a file that is not a valid replication instance file.
mupip ftok -jnlpool <filename>
MUPIP FTOK looks at the replication instance file defined by the ydb_repl_instance environment variable. And not at the input file name specified. It would be nice to honor the input file name and treat that as an instance file instead of deriving it from the environment variable.
Whils the current behavior was okay when there was just one replication instance file, with GTM-8182 changes in GT.M V6.3-003, a process can access multiple instance files and so it would be desirable for MUPIP FTOK to also recognize multiple instance files.
Draft Release Note
MUPIP FTOK -JNLPOOL and MUPIP FTOK -RECVPOOL operate on the specified instance-file-name. Previously they used to ignore the input instance-file-name and always operate on the instance file name derived from the ydb_repl_instance (or gtm_repl_instance) environment variable.
Final Release Note
Description
The below command currently works even though does not exist in the file system or if it points to a file that is not a valid replication instance file.
MUPIP FTOK looks at the replication instance file defined by the ydb_repl_instance environment variable. And not at the input file name specified. It would be nice to honor the input file name and treat that as an instance file instead of deriving it from the environment variable.
Whils the current behavior was okay when there was just one replication instance file, with GTM-8182 changes in GT.M V6.3-003, a process can access multiple instance files and so it would be desirable for MUPIP FTOK to also recognize multiple instance files.
Draft Release Note
MUPIP FTOK -JNLPOOL and MUPIP FTOK -RECVPOOL operate on the specified instance-file-name. Previously they used to ignore the input instance-file-name and always operate on the instance file name derived from the ydb_repl_instance (or gtm_repl_instance) environment variable.