In our DB2 V13 /lpp/db2d/mql/ directory there are no sub directories . Especially the listener directory with the db2mqln1 and db2mqln2 executables. Instead there is only a tar file. I assume that it has to be untared to create the directories and the executables.
I will keep you posted. THANK YOU SO MUCH for your pointers.
Original Message:
Sent: Thu May 29, 2025 04:15 AM
From: Diego Cardalliaguet
Subject: Unix files during V13 Upgrade - General question
There must be a Java classpath somewhere pointing to the old v12 path. You must check all the tasks where the listener is executed (command lists, JCLs, automations, user profiles…) from where the java jars are loaded.
A classpath is mostly like a STEPLIB, it must point to the correct modules or will execute the wrong version or even fail.
You can enable some error processing following this MQListener error processing
Ibm | remove preview |
| MQListener error processing | MQListener reads from IBM MQ message queues and calls Db2 stored procedures with those messages. If any errors occur during this process and the message is to be sent to the deadletter queue, MQListener returns a reason code to the deadletter queue. | View this on Ibm > |
|
|
Also, I would review the MQListener configuration for the case something has been deprecated https://www.ibm.com/docs/en/db2-for-zos/13.0.0?topic=zos-mqlistener-in-db2
Regards,
------------------------------
Diego Cardalliaguet
IBM Data&AI zStack Leader for EMEA
IBM
Original Message:
Sent: Thu May 29, 2025 04:09 AM
From: Ramachandran Subramanian
Subject: Unix files during V13 Upgrade - General question
Thank you so much for answering my question in a simple way. Is it correct for me to think of these Unix files as the foundational files ( executables, macros and cuslibs) needed for DB2 to talk to the non mainframe world? I assume MQL is for MQ-Listner.
After the DB2 V13 upgrade with the V13 unix files our MQ-Listner task fails ... If I unmount the V13 unix files and remount the V12 unix files, it works with DB2V13.
I would be grateful for any pointers you can give to trace the issue and resolve it.
Menu Utilities Compilers Help
BROWSE /tmp/db2s_mqlsn.err
Command ===>
********************************* Top of Dat
db2mqln2: FSUM7351 not found
******************************** Bottom of D
Display Filter View Print Options Search Help
-------------------------------------------------------------------------------
SDSF OUTPUT DISPLAY DB2SMQL1 STC44190 DSID 1 LINE 0 COLS 02- 81
COMMAND INPUT ===> SCROLL ===> CSR
********************************* TOP OF DATA **********************************
//DB2SMQL1 JOB MSGLEVEL=1 STC44190
//STARTING EXEC DB2SMQL1
J E S 2 J O B L O G -- S Y S T E M A L F 0 -- N O D E
16.47.06 STC44190 ---- WEDNESDAY, 28 MAY 2025 ----
16.47.06 STC44190 IEF695I START DB2SMQL1 WITH JOBNAME DB2SMQL1 IS ASSIGNED TO U
16.47.06 STC44190 $HASP373 DB2SMQL1 STARTED
16.47.06 STC44190 IEF403I DB2SMQL1 - STARTED - TIME=16.47.06
16.47.06 STC44190 - ----TIMINGS (MINUTES)-
16.47.06 STC44190 -STEPNAME PROCSTEP RC EXCP CONN TCB SRB C
16.47.06 STC44190 - RNSCRPT 00 114 1 0.000026 0.000000
16.47.06 STC44190 - *OMVSEX 00 67 0 0.000027 0.000000
16.47.06 STC44190 - *OMVSEX 127 1222 0 0.000125 0.000000
16.47.06 STC44190 IEF404I DB2SMQL1 - ENDED - TIME=16.47.06
16.47.06 STC44190 -DB2SMQL1 ENDED. NAME- TOTAL TCB CPU TIM
16.47.06 STC44190 $HASP395 DB2SMQL1 ENDED - RC=0127
------ JES2 JOB STATISTICS ------
28 MAY 2025 JOB EXECUTION DATE
2 CARDS READ
96 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
13 SYSOUT SPOOL KBYTES
0.00 MINUTES EXECUTION TIME
1 //DB2SMQL1 JOB MSGLEVEL=1
2 //STARTING EXEC DB2SMQL1
3 XXDB2SMQL1 PROC
XX* START MQ-Listener
4 XXRNSCRPT EXEC PGM=BPXBATCH,REGION=0M
5 XXSTDIN DD PATH='/u/al/public/db/listener/db2mqln_run.cmd',
XX PATHOPTS=(ORDONLY)
6 XXSTDOUT DD PATH='/tmp/db2s_mqlsn.out',
XX PATHOPTS=(OWRONLY,OCREAT),
XX PATHMODE=(SIRWXU,SIRWXG,SIROTH)
7 XXSTDERR DD PATH='/tmp/db2s_mqlsn.err',
XX PATHOPTS=(OWRONLY,OCREAT),
XX PATHMODE=(SIRWXU,SIRWXG,SIROTH)
STMT NO. MESSAGE
BROWSE /tmp/db2s_mqlsn.out Line 0000000000 Col 001 080
Command ===> Scroll ===> CSR
********************************* Top of Data **********************************
Setting DB2 config
Syslogd daemon interface will be used for logging
Syslogd daemon interface will be used for logging
Syslogd daemon interface will be used for logging
2025-05-28::17:17:39=> DSNQ073I MQListener started a thread running the task spe
2025-05-28::09:29:23=> DSNQ081I MQListener received a shutdown message on admin
2025-05-28::09:29:24=> DSNQ074I A thread running the task specified in the confi
******************************** Bottom of Data ********************************
------------------------------
Ramachandran Subramanian
Original Message:
Sent: Thu May 29, 2025 01:30 AM
From: Diego Cardalliaguet
Subject: Unix files during V13 Upgrade - General question
Hi there,
They are used for several different things to enable java, jdbc access, web services or API providing…
As an example:
../worf
folder enables web services: https://www.ibm.com/docs/en/db2-for-zos/13.0.0?topic=services-enabling-db2-as-web-service-provider
Some others enable Java and you configure them through a panel: https://www.ibm.com/docs/en/db2-for-zos/13.0.0?topic=session-dsntipx1-db2-java-properties-panel
AWI is the acronym of auxiliary work information…
The question here is that USS has become more and more used through the years because it provides what it was intended for in the late 90's, which is giving z/OS the capability of interacting with external systems and enabling functionalities that need to be compatible (or are coming from) other platforms.
Same applies to Java. IBM Z is a great platform to run Java because it performs very well and, more and more, z/OS and subsystems are using it to enable features. zOSMF is a good example of how even the operative system uses it.
Hope it helps.
------------------------------
Diego Cardalliaguet
IBM Data&AI zStack Leader for EMEA
IBM
Original Message:
Sent: Wed May 28, 2025 03:46 AM
From: Ramachandran Subramanian
Subject: Unix files during V13 Upgrade - General question
Hello,
Kindly forgive my ignorance about JAVA . I am trying to understand why do we need these files when we upgrade to V13?
Are they like the JDBC drivers that exist on the mainframe when there is a JAVA program running on the mainframe ?
In a normal PC to mainframe world ( with traditional DB2 connect ) the drivers are installed on the PC. Is this the mainframe equivalent?
. . . . . . . . . . . . . . . . .
ALF0 Dilectoly List
/lpp/db2d10_D10A/
Select one or more files with / or action codes.
. Type Filename
_ Dir .
_ Dir ..
_ Dir awi
_ Dir base
_ Dir jdbc
_ Dir mql
_ Dir worf
. . . . . . . . . . . . . . . . .
ALF0 Dilectoly List
/lpp/db2d10_D10A/awi/
Select one or more files with / or action codes.
. Type Filename
_ Dir .
_ Dir ..
_ File dsndqjst.awi
_ File dsndqlst.awi
_ File dsndqtgs.awi
_ File dsndqtst.awi
_ File dsndqtxa.awi
_ File dsndqwha.awi
_ File dsndqwhs.awi
_ File dsndqwsa.awi
_ File dsndqwsd.awi
_ File dsndqwst.awi
_ File dsndqws0.awi
_ File dsndqws1.awi
_ File dsndqxst.awi
_ File dsndq3st.awi
_ Dir IBM
. . . . . . . . . . . . . . . . .
ALF0 Dilectoly List
/lpp/db2d10_D10A/jdbc/
Select one or more files with / or action codes.
. Type Filename
_ Dir .
_ Dir ..
_ Dir bin
_ Dir classes
_ Dir IBM
_ Dir lib
_ File README
_ Dir samples
------------------------------
Ramachandran Subramanian
------------------------------