DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Chris Hoelscher

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
Good day - I am attempting to capture start/stop database activity
For the first such command I encounter (thru an ejes console emulator batch job) I get

DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607
HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)
Followed by
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

For subsequent start or stop commands I only see the
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION
DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION

And not the ASYNCHRONOUS message

Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?
If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?

If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support

Thank you very much,

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
Humana Inc.
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 476-2538 or 407-7266

Roy Boxwell

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
(in response to Chris Hoelscher)
It depends on what task issue the STOP command. If you issue it from a batch connection then it is ASYNC but online is SYNC – the idea being that in online you can afford to wait while it stops... This also means that after the Batch STOP the DB could be in STOPP (Stop Pending) status and not actually stopped! You have to do DISPLAY commands until it finally gets into STOP status... been caught by this before!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich



From: Chris Hoelscher [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 3:12 AM
To: [login to unmask email]
Subject: [DB2-L] - DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??



Good day – I am attempting to capture start/stop database activity

For the first such command I encounter (thru an ejes console emulator batch job) I get



DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607

HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)

Followed by

DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION



For subsequent start or stop commands I only see the

DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION



And not the ASYNCHRONOUS message



Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?

If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?



If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support



Thank you very much,



Chris Hoelscher

Technology Architect, Database Infrastructure Services

Technology Solution Services

Humana Inc.

123 East Main Street

Louisville, KY 40202

Humana.com

(502) 476-2538 or 407-7266




The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and
do not discriminate on the basis of race, color, national origin, age, disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national origin, age,
disability, sex, sexual orientation, gender identity, or religion.

English: ATTENTION: If you do not speak English, language assistance services, free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.

-----End Original Message-----

Attachments

  • smime.p7s (5.1k)

Philip Sevetson

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
(in response to Roy Boxwell)
This does not give me a warm and fuzzy feeling.


1) The Batch/Online difference should be _options_, not _context_. If you want to issue a STOP and not worry about it, you should have an option WAIT(NO) for it (or WAIT(YES) which should be a default). Likewise, if you want a batch process to wait, you should be permitted to set the command.

2) Not logging a command _sometimes_ is an extremely poor design decision which will cause all kinds of trouble with console automation and reporting.

--Phil Sevetson
(IBM Coder in every job since 1983)

From: Boxwell, Roy [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 1:51 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

It depends on what task issue the STOP command. If you issue it from a batch connection then it is ASYNC but online is SYNC – the idea being that in online you can afford to wait while it stops... This also means that after the Batch STOP the DB could be in STOPP (Stop Pending) status and not actually stopped! You have to do DISPLAY commands until it finally gets into STOP status... been caught by this before!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

From: Chris Hoelscher [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 3:12 AM
To: [login to unmask email]
Subject: [DB2-L] - DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Good day – I am attempting to capture start/stop database activity
For the first such command I encounter (thru an ejes console emulator batch job) I get

DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607
HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)
Followed by
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

For subsequent start or stop commands I only see the
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION
DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION

And not the ASYNCHRONOUS message

Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?
If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?

If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support

Thank you very much,

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
Humana Inc.
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 476-2538 or 407-7266


The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and
do not discriminate on the basis of race, color, national origin, age, disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national origin, age,
disability, sex, sexual orientation, gender identity, or religion.

English: ATTENTION: If you do not speak English, language assistance services, free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**

Raymond Bell

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
(in response to Philip Sevetson)
Brace for disappointment, Phil. I believe it was ever thus. Batch is asynch and just ‘cause it’s issued the command doesnae mean it’s actually been effected yet. TSO is synch and will wait until the command has indeed worked before telling you so.

Call it WAD. :o)

Cheers,


Raymond

From: Sevetson, Phil [mailto:[login to unmask email]
Sent: 08 February 2019 13:03
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

This does not give me a warm and fuzzy feeling.


1) The Batch/Online difference should be _options_, not _context_. If you want to issue a STOP and not worry about it, you should have an option WAIT(NO) for it (or WAIT(YES) which should be a default). Likewise, if you want a batch process to wait, you should be permitted to set the command.

2) Not logging a command _sometimes_ is an extremely poor design decision which will cause all kinds of trouble with console automation and reporting.

--Phil Sevetson
(IBM Coder in every job since 1983)

From: Boxwell, Roy [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 1:51 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

It depends on what task issue the STOP command. If you issue it from a batch connection then it is ASYNC but online is SYNC – the idea being that in online you can afford to wait while it stops... This also means that after the Batch STOP the DB could be in STOPP (Stop Pending) status and not actually stopped! You have to do DISPLAY commands until it finally gets into STOP status... been caught by this before!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

From: Chris Hoelscher [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 3:12 AM
To: [login to unmask email]
Subject: [DB2-L] - DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Good day – I am attempting to capture start/stop database activity
For the first such command I encounter (thru an ejes console emulator batch job) I get

DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607
HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)
Followed by
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

For subsequent start or stop commands I only see the
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION
DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION

And not the ASYNCHRONOUS message

Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?
If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?

If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support

Thank you very much,

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
Humana Inc.
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 476-2538 or 407-7266


The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and
do not discriminate on the basis of race, color, national origin, age, disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national origin, age,
disability, sex, sexual orientation, gender identity, or religion.

English: ATTENTION: If you do not speak English, language assistance services, free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Roy Boxwell

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
(in response to Philip Sevetson)
It is all logged...it just doesnt STOP instantly like some coders and software thinks it does....



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich



From: Sevetson, Phil [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 2:03 PM
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??



This does not give me a warm and fuzzy feeling.



1) The Batch/Online difference should be _options_, not _context_. If you want to issue a STOP and not worry about it, you should have an option WAIT(NO) for it (or WAIT(YES) which should be a default). Likewise, if you want a batch process to wait, you should be permitted to set the command.

2) Not logging a command _sometimes_ is an extremely poor design decision which will cause all kinds of trouble with console automation and reporting.



--Phil Sevetson

(IBM Coder in every job since 1983)



From: Boxwell, Roy [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 1:51 AM
To: [login to unmask email] <mailto:[login to unmask email]>
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??



It depends on what task issue the STOP command. If you issue it from a batch connection then it is ASYNC but online is SYNC – the idea being that in online you can afford to wait while it stops... This also means that after the Batch STOP the DB could be in STOPP (Stop Pending) status and not actually stopped! You have to do DISPLAY commands until it finally gets into STOP status... been caught by this before!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich



From: Chris Hoelscher [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 3:12 AM
To: [login to unmask email] <mailto:[login to unmask email]>
Subject: [DB2-L] - DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??



Good day – I am attempting to capture start/stop database activity

For the first such command I encounter (thru an ejes console emulator batch job) I get



DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607

HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)

Followed by

DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION



For subsequent start or stop commands I only see the

DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION



And not the ASYNCHRONOUS message



Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?

If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?



If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support



Thank you very much,



Chris Hoelscher

Technology Architect, Database Infrastructure Services

Technology Solution Services

Humana Inc.

123 East Main Street

Louisville, KY 40202

Humana.com

(502) 476-2538 or 407-7266




The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and
do not discriminate on the basis of race, color, national origin, age, disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national origin, age,
disability, sex, sexual orientation, gender identity, or religion.

English: ATTENTION: If you do not speak English, language assistance services, free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.

-----End Original Message-----

**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**

-----End Original Message-----

Attachments

  • smime.p7s (5.1k)

Philip Sevetson

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
(in response to Raymond Bell)
Raymond,

Not disagreeing with what you’re saying. I understand Roy’s comment about the way it **does** work. I can’t argue with that and I’m not trying.

I absolutely refuse to accept that it’s a **good idea** that it works this way (and I know you’re not arguing that!). My concerns are:

1) ASYNC is occurring without being logged in subsequent STOP commands. This is an irregular behavior, which is hell for automation tools to understand and has to be encoded everywhere you might need to look for it. Worst case, it amounts to a lie of omission as far as actually informing the system and monitors about the state of DB2 objects.

2) Not having a synchronous STOP command available in batch will complicate attempts to minimize an outage for any of several tasks: backup, maintenance, any kind of under-the-hood* operation which needs an actual STOP, not a STOPP.

Regards, and TGIF,

-Phil S.

* U.S. slang: inside the engine compartment of a motor vehicle. Do yours still call that a “bonnet”?

From: Bell, Raymond (Hosting Services, Technology) [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 8:13 AM
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Brace for disappointment, Phil. I believe it was ever thus. Batch is asynch and just ‘cause it’s issued the command doesnae mean it’s actually been effected yet. TSO is synch and will wait until the command has indeed worked before telling you so.

Call it WAD. :o)

Cheers,


Raymond

From: Sevetson, Phil [mailto:[login to unmask email]
Sent: 08 February 2019 13:03
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

This does not give me a warm and fuzzy feeling.


1) The Batch/Online difference should be _options_, not _context_. If you want to issue a STOP and not worry about it, you should have an option WAIT(NO) for it (or WAIT(YES) which should be a default). Likewise, if you want a batch process to wait, you should be permitted to set the command.

2) Not logging a command _sometimes_ is an extremely poor design decision which will cause all kinds of trouble with console automation and reporting.

--Phil Sevetson
(IBM Coder in every job since 1983)

From: Boxwell, Roy [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 1:51 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

It depends on what task issue the STOP command. If you issue it from a batch connection then it is ASYNC but online is SYNC – the idea being that in online you can afford to wait while it stops... This also means that after the Batch STOP the DB could be in STOPP (Stop Pending) status and not actually stopped! You have to do DISPLAY commands until it finally gets into STOP status... been caught by this before!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

From: Chris Hoelscher [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 3:12 AM
To: [login to unmask email]
Subject: [DB2-L] - DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Good day – I am attempting to capture start/stop database activity
For the first such command I encounter (thru an ejes console emulator batch job) I get

DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607
HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)
Followed by
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

For subsequent start or stop commands I only see the
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION
DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION

And not the ASYNCHRONOUS message

Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?
If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?

If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support

Thank you very much,

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
Humana Inc.
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 476-2538 or 407-7266


The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and
do not discriminate on the basis of race, color, national origin, age, disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national origin, age,
disability, sex, sexual orientation, gender identity, or religion.

English: ATTENTION: If you do not speak English, language assistance services, free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.


Visit our website at www.rbs.com http://www.rbs.com
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**

Raymond Bell

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
(in response to Philip Sevetson)
Yo Phil,

Quite agree. It ain’t necessarily the right way, but it is how it is. :o)

Yeah, it would be good to have the option for batch –STOp (and other) commands to be synchronously performed. Is there some underlying architectural reason why a batch job can’t wait to receive the actual ‘it’s now stopped’ message I wonder? Dunno. But yes, it’s not helpful that you might, or might not, wait for the –STOp to actually work before getting a response back from Db2 depending on how you issued the command.

TGIF indeed! WFH today so a long arduous trek home after work when I’m done i.e. wandering downstairs. To the gentle tinkle of Tanqueray and Fever Tree. ;o)

Cheers,


Raymond
PS: It is indeed the ‘bonnet’. A ‘hood’ is where scallywags come from.

From: Sevetson, Phil [mailto:[login to unmask email]
Sent: 08 February 2019 13:27
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Raymond,

Not disagreeing with what you’re saying. I understand Roy’s comment about the way it **does** work. I can’t argue with that and I’m not trying.

I absolutely refuse to accept that it’s a **good idea** that it works this way (and I know you’re not arguing that!). My concerns are:

1) ASYNC is occurring without being logged in subsequent STOP commands. This is an irregular behavior, which is hell for automation tools to understand and has to be encoded everywhere you might need to look for it. Worst case, it amounts to a lie of omission as far as actually informing the system and monitors about the state of DB2 objects.

2) Not having a synchronous STOP command available in batch will complicate attempts to minimize an outage for any of several tasks: backup, maintenance, any kind of under-the-hood* operation which needs an actual STOP, not a STOPP.

Regards, and TGIF,

-Phil S.

* U.S. slang: inside the engine compartment of a motor vehicle. Do yours still call that a “bonnet”?

From: Bell, Raymond (Hosting Services, Technology) [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 8:13 AM
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Brace for disappointment, Phil. I believe it was ever thus. Batch is asynch and just ‘cause it’s issued the command doesnae mean it’s actually been effected yet. TSO is synch and will wait until the command has indeed worked before telling you so.

Call it WAD. :o)

Cheers,


Raymond

From: Sevetson, Phil [mailto:[login to unmask email]
Sent: 08 February 2019 13:03
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

This does not give me a warm and fuzzy feeling.


1) The Batch/Online difference should be _options_, not _context_. If you want to issue a STOP and not worry about it, you should have an option WAIT(NO) for it (or WAIT(YES) which should be a default). Likewise, if you want a batch process to wait, you should be permitted to set the command.

2) Not logging a command _sometimes_ is an extremely poor design decision which will cause all kinds of trouble with console automation and reporting.

--Phil Sevetson
(IBM Coder in every job since 1983)

From: Boxwell, Roy [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 1:51 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

It depends on what task issue the STOP command. If you issue it from a batch connection then it is ASYNC but online is SYNC – the idea being that in online you can afford to wait while it stops... This also means that after the Batch STOP the DB could be in STOPP (Stop Pending) status and not actually stopped! You have to do DISPLAY commands until it finally gets into STOP status... been caught by this before!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

From: Chris Hoelscher [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 3:12 AM
To: [login to unmask email]
Subject: [DB2-L] - DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Good day – I am attempting to capture start/stop database activity
For the first such command I encounter (thru an ejes console emulator batch job) I get

DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607
HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)
Followed by
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

For subsequent start or stop commands I only see the
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION
DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION

And not the ASYNCHRONOUS message

Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?
If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?

If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support

Thank you very much,

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
Humana Inc.
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 476-2538 or 407-7266


The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and
do not discriminate on the basis of race, color, national origin, age, disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national origin, age,
disability, sex, sexual orientation, gender identity, or religion.

English: ATTENTION: If you do not speak English, language assistance services, free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.


Visit our website at www.rbs.com http://www.rbs.com
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Phil Grainger

DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??
(in response to Raymond Bell)
Which is also why many (all?) of the tools around Db2 have to engineer a “-STOP” followed by an iteration of “is it stopped yet?” queries until the stop has indeed been completed
________________________________





[BMC Exchange 2019 - Global Event Series - REGISTER] https://www.bmc.com/ami

Phil Grainger
Principal Enablement Manager

Direct

+44 1189 218 000

Mobile

+44 7808 643 479

Email

[login to unmask email]

E2, Eskdale Road
Winnersh
Berkshire
United Kingdom
RG41 5TS
[image001 (002)][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png]










































From: Bell, Raymond (Hosting Services, Technology) [mailto:[login to unmask email]
Sent: 08 February 2019 16:02
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Yo Phil,

Quite agree. It ain’t necessarily the right way, but it is how it is. :o)

Yeah, it would be good to have the option for batch –STOp (and other) commands to be synchronously performed. Is there some underlying architectural reason why a batch job can’t wait to receive the actual ‘it’s now stopped’ message I wonder? Dunno. But yes, it’s not helpful that you might, or might not, wait for the –STOp to actually work before getting a response back from Db2 depending on how you issued the command.

TGIF indeed! WFH today so a long arduous trek home after work when I’m done i.e. wandering downstairs. To the gentle tinkle of Tanqueray and Fever Tree. ;o)

Cheers,


Raymond
PS: It is indeed the ‘bonnet’. A ‘hood’ is where scallywags come from.

From: Sevetson, Phil [mailto:[login to unmask email]
Sent: 08 February 2019 13:27
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Raymond,

Not disagreeing with what you’re saying. I understand Roy’s comment about the way it **does** work. I can’t argue with that and I’m not trying.

I absolutely refuse to accept that it’s a **good idea** that it works this way (and I know you’re not arguing that!). My concerns are:

1. ASYNC is occurring without being logged in subsequent STOP commands. This is an irregular behavior, which is hell for automation tools to understand and has to be encoded everywhere you might need to look for it. Worst case, it amounts to a lie of omission as far as actually informing the system and monitors about the state of DB2 objects.
2. Not having a synchronous STOP command available in batch will complicate attempts to minimize an outage for any of several tasks: backup, maintenance, any kind of under-the-hood* operation which needs an actual STOP, not a STOPP.

Regards, and TGIF,

-Phil S.

* U.S. slang: inside the engine compartment of a motor vehicle. Do yours still call that a “bonnet”?

From: Bell, Raymond (Hosting Services, Technology) [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 8:13 AM
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Brace for disappointment, Phil. I believe it was ever thus. Batch is asynch and just ‘cause it’s issued the command doesnae mean it’s actually been effected yet. TSO is synch and will wait until the command has indeed worked before telling you so.

Call it WAD. :o)

Cheers,


Raymond

From: Sevetson, Phil [mailto:[login to unmask email]
Sent: 08 February 2019 13:03
To: '[login to unmask email]'
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

This does not give me a warm and fuzzy feeling.


1. The Batch/Online difference should be _options_, not _context_. If you want to issue a STOP and not worry about it, you should have an option WAIT(NO) for it (or WAIT(YES) which should be a default). Likewise, if you want a batch process to wait, you should be permitted to set the command.
2. Not logging a command _sometimes_ is an extremely poor design decision which will cause all kinds of trouble with console automation and reporting.

--Phil Sevetson
(IBM Coder in every job since 1983)

From: Boxwell, Roy [mailto:[login to unmask email]
Sent: Friday, February 08, 2019 1:51 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

It depends on what task issue the STOP command. If you issue it from a batch connection then it is ASYNC but online is SYNC – the idea being that in online you can afford to wait while it stops... This also means that after the Batch STOP the DB could be in STOPP (Stop Pending) status and not actually stopped! You have to do DISPLAY commands until it finally gets into STOP status... been caught by this before!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de https://urldefense.proofpoint.com/v2/url?u=http-3A__www.seg.de_&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=AiTYfFf97ibjs-2eTf0dBjXeFHxDEnFJdFab7WiwelQ&s=FNiJUiPn4yze2txH_6tZG5w5AQsRvaTFQieu2mmHoJk&e=
Link zur Datenschutzerklärung https://urldefense.proofpoint.com/v2/url?u=https-3A__www.seg.de_corporate_rechtliche-2Dhinweise_datenschutz_&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=AiTYfFf97ibjs-2eTf0dBjXeFHxDEnFJdFab7WiwelQ&s=2FE3DoO_GnKOe7yiYNyCgVdC_K1pOLO0GYVcrusgLWU&e=

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich

From: Chris Hoelscher [mailto:[login to unmask email]
Sent: Friday, February 8, 2019 3:12 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - DB2 11 FOR Z/os nfm: only first asynchronous command written to MSTR jeslog ??

Good day – I am attempting to capture start/stop database activity
For the first such command I encounter (thru an ejes console emulator batch job) I get

DSNT736I *DBT3 ASYNCHRONOUS STOP DATABASE COMMAND 607
HAS COMPLETED FOR COMMAND: STOP DB(xxxxxxxx)
Followed by
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION

For subsequent start or stop commands I only see the
DSN9022I *DBT3 DSNTDDIS 'STOP DATABASE' NORMAL COMPLETION
DSN9022I *DBT3 DSNTDDIS 'START DATABASE' NORMAL COMPLETION

And not the ASYNCHRONOUS message

Is this working as designed? Is only the first ASYNC message intended to be displayed to the MSTR jeslog?
If so, is there a zparm/trick to Force ALL ASYNC commands to be displayed to the MSTR jeslog?

If the general opinion is that this is NOT working as designed, I will indeed open an issue with IBM DB2 support

Thank you very much,

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
Humana Inc.
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 476-2538 or 407-7266


The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and
do not discriminate on the basis of race, color, national origin, age, disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national origin, age,
disability, sex, sexual orientation, gender identity, or religion.

English: ATTENTION: If you do not speak English, language assistance services, free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.


Visit our website at www.rbs.com https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rbs.com_&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=AiTYfFf97ibjs-2eTf0dBjXeFHxDEnFJdFab7WiwelQ&s=Sb2Neb-RoR-MtVCX0JFci5wNPX2RXObRSE2lHTQhPHo&e=
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.


Visit our website at www.rbs.com https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rbs.com_&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=EAGrd_qzLADPfI8dgytr8sbCG7_U9QfXwQMLgK1Zo30&m=AiTYfFf97ibjs-2eTf0dBjXeFHxDEnFJdFab7WiwelQ&s=Sb2Neb-RoR-MtVCX0JFci5wNPX2RXObRSE2lHTQhPHo&e=
-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.
Attachments

  • image001.jpg (49.7k)
  • image008.png (6.7k)
  • image009.png (3.7k)
  • image010.png (<1k)