Native RESTful service - BIND?

Wolfgang Beikircher

Native RESTful service - BIND?

Hi there!

I attended the last IDUG on Malta and heard of the 'native RESTful services' that were ported to V11. Actually we are searching for an easy way to define standardized SQL queries from our 'distributed programming people'. Today we have, at least for inhouse written software, no dynamic SQL on Db2. If data is requested from Db2 there has to be written a Stored procedure or a CICS/batch program.

Since we have just static SQL we could establish a quite good QA that checks the statements already in our test environments. So far so good.

Now to the question. Is there a way to intefere the creation of a service (created through the native RESTful interface) to do some checks for QA? I have an exit in mind, that allows us to perform some explain.

 

Thanks

 

 

 

 

Walter Janißen

AW: Native RESTful service - BIND?
(in response to Wolfgang Beikircher)
Hi

AFAIK you will get a package for that service in SYSPACKAGE, which you can rebind with EXPLAIN(YES) or you can specify EXPLAIN(YES) or so when you create that RESTful API

Kind regards
Walter Janißen [standard_IBM+Champ+7+Yr+Analytics]

ITERGO Informationstechnologie GmbH
Anwendungsentwicklung
Technische Anwendungsarchitektur
Victoriaplatz 2
D-40198 Düsseldorf
[login to unmask email]<mailto:[login to unmask email]>

ITERGO Informationstechnologie GmbH
Vorsitzender des Aufsichtsrats: Christian Diedrich
Geschäftsführung: Dr. Bettina Anders (Vorsitzende),
Lothar Engelke, Ina Kirchhof, Dr. Michael Regauer
Sitz: Düsseldorf, Handelsregister: Amtsgericht Düsseldorf HRB 37996

Von: Wolfgang Beikircher <[login to unmask email]>
Gesendet: Montag, 19. November 2018 15:45
An: [login to unmask email]
Betreff: [DB2-L] - Native RESTful service - BIND?


Hi there!

I attended the last IDUG on Malta and heard of the 'native RESTful services' that were ported to V11. Actually we are searching for an easy way to define standardized SQL queries from our 'distributed programming people'. Today we have, at least for inhouse written software, no dynamic SQL on Db2. If data is requested from Db2 there has to be written a Stored procedure or a CICS/batch program.

Since we have just static SQL we could establish a quite good QA that checks the statements already in our test environments. So far so good.

Now to the question. Is there a way to intefere the creation of a service (created through the native RESTful interface) to do some checks for QA? I have an exit in mind, that allows us to perform some explain.



Thanks









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

  • image001.png (2.6k)

Raymond Bell

Native RESTful service - BIND?
(in response to Wolfgang Beikircher)
Hi Wolfgang,

First off, if you’re not bang up-to-date with Db2 maintenance I suggest you be so. There’s an info APAR (II14827) that highlights a few gems, but if you want any of the more useful bind parms to work with BIND SERVICE (other than OWNER and QUALIFIER) you’ll need some. Plus some PTFs to even get it to work at all.

So. I’m looking at using Endevor to manage the single SQL statement REST service and have it perform the required BIND SERVICE to register it. Any QA performed would be after the fact, as per any other package that gets bound. Not sure about intercepting the bind per se but you could certainly establish change management processes to QA the package and get it signed off/modified before going above Unit Test.

Have fun. And brace for a bumpy ride. An update I received in a V11 PMR I raised on REST bind options said, ‘…it's a relative new service and is constantly improved…’ to which you could replace ‘improved’ with ‘being fixed’. Still it’s worth persevering with BIND SERVICE as the alternative (off-host creation of services via something like Postman) is quite fiddly, can’t really be automated and you have no control over the bind options used – although of course you could always rebind the package afterwards to get the parms you want.

Cheers,


Raymond


From: Wolfgang Beikircher [mailto:[login to unmask email]
Sent: 19 November 2018 14:45
To: [login to unmask email]
Subject: [DB2-L] - Native RESTful service - BIND?


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************


Hi there!

I attended the last IDUG on Malta and heard of the 'native RESTful services' that were ported to V11. Actually we are searching for an easy way to define standardized SQL queries from our 'distributed programming people'. Today we have, at least for inhouse written software, no dynamic SQL on Db2. If data is requested from Db2 there has to be written a Stored procedure or a CICS/batch program.

Since we have just static SQL we could establish a quite good QA that checks the statements already in our test environments. So far so good.

Now to the question. Is there a way to intefere the creation of a service (created through the native RESTful interface) to do some checks for QA? I have an exit in mind, that allows us to perform some explain.



Thanks









-----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

Patrick Bossman

RE: Native RESTful service - BIND?
(in response to Raymond Bell)

Rest calls can be automated.  We automated the deployment with UCD. 

In Reply to Raymond Bell:

Hi Wolfgang,

First off, if you’re not bang up-to-date with Db2 maintenance I suggest you be so. There’s an info APAR (II14827) that highlights a few gems, but if you want any of the more useful bind parms to work with BIND SERVICE (other than OWNER and QUALIFIER) you’ll need some. Plus some PTFs to even get it to work at all.

So. I’m looking at using Endevor to manage the single SQL statement REST service and have it perform the required BIND SERVICE to register it. Any QA performed would be after the fact, as per any other package that gets bound. Not sure about intercepting the bind per se but you could certainly establish change management processes to QA the package and get it signed off/modified before going above Unit Test.

Have fun. And brace for a bumpy ride. An update I received in a V11 PMR I raised on REST bind options said, ‘…it's a relative new service and is constantly improved…’ to which you could replace ‘improved’ with ‘being fixed’. Still it’s worth persevering with BIND SERVICE as the alternative (off-host creation of services via something like Postman) is quite fiddly, can’t really be automated and you have no control over the bind options used – although of course you could always rebind the package afterwards to get the parms you want.

Cheers,


Raymond


From: Wolfgang Beikircher [mailto:[login to unmask email]
Sent: 19 November 2018 14:45
To: [login to unmask email]
Subject: [DB2-L] - Native RESTful service - BIND?


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************


Hi there!

I attended the last IDUG on Malta and heard of the 'native RESTful services' that were ported to V11. Actually we are searching for an easy way to define standardized SQL queries from our 'distributed programming people'. Today we have, at least for inhouse written software, no dynamic SQL on Db2. If data is requested from Db2 there has to be written a Stored procedure or a CICS/batch program.

Since we have just static SQL we could establish a quite good QA that checks the statements already in our test environments. So far so good.

Now to the question. Is there a way to intefere the creation of a service (created through the native RESTful interface) to do some checks for QA? I have an exit in mind, that allows us to perform some explain.



Thanks









-----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

Raymond Bell

Native RESTful service - BIND?
(in response to Patrick Bossman)
Their deployment can be automated via Endevor too, which is what we’re working on doing. I meant automatic deployment via Postman in particular (which is what we have at our disposal) would be difficult as it’s an interactive process but until we have deployed the Db2 maintenance we need that’s all we have right now.

From: Patrick Bossman [mailto:[login to unmask email]
Sent: 20 November 2018 12:20
To: [login to unmask email]
Subject: [DB2-L] - RE: Native RESTful service - BIND?


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************


Rest calls can be automated. We automated the deployment with UCD.

In Reply to Raymond Bell:
Hi Wolfgang,

First off, if you’re not bang up-to-date with Db2 maintenance I suggest you be so. There’s an info APAR (II14827) that highlights a few gems, but if you want any of the more useful bind parms to work with BIND SERVICE (other than OWNER and QUALIFIER) you’ll need some. Plus some PTFs to even get it to work at all.

So. I’m looking at using Endevor to manage the single SQL statement REST service and have it perform the required BIND SERVICE to register it. Any QA performed would be after the fact, as per any other package that gets bound. Not sure about intercepting the bind per se but you could certainly establish change management processes to QA the package and get it signed off/modified before going above Unit Test.

Have fun. And brace for a bumpy ride. An update I received in a V11 PMR I raised on REST bind options said, ‘…it's a relative new service and is constantly improved…’ to which you could replace ‘improved’ with ‘being fixed’. Still it’s worth persevering with BIND SERVICE as the alternative (off-host creation of services via something like Postman) is quite fiddly, can’t really be automated and you have no control over the bind options used – although of course you could always rebind the package afterwards to get the parms you want.

Cheers,


Raymond


From: Wolfgang Beikircher [mailto:[login to unmask email]
Sent: 19 November 2018 14:45
To: [login to unmask email]
Subject: [DB2-L] - Native RESTful service - BIND?


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************


Hi there!

I attended the last IDUG on Malta and heard of the 'native RESTful services' that were ported to V11. Actually we are searching for an easy way to define standardized SQL queries from our 'distributed programming people'. Today we have, at least for inhouse written software, no dynamic SQL on Db2. If data is requested from Db2 there has to be written a Stored procedure or a CICS/batch program.

Since we have just static SQL we could establish a quite good QA that checks the statements already in our test environments. So far so good.

Now to the question. Is there a way to intefere the creation of a service (created through the native RESTful interface) to do some checks for QA? I have an exit in mind, that allows us to perform some explain.



Thanks









-----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

-----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

Anthony Ciabattoni

Native RESTful service - BIND?
(in response to Raymond Bell)
Hello Wolfgang,



I agree with Raymond 100% in regards to keeping an eye on the REST info

APAR and be as current as you can in the Db2 Native REST space. It is very

dynamic area and there has been and will be many useful enhancements being

delivered in the maintenance stream. The most current APARS that have been

made available has supplied significant performance benefits and

STOP/START/DISPLAY RESTSVC capabilities.





Regards,

Anthony







Anthony Ciabattoni

Senior IT Specialist

Db2 for z/OS Development SWAT Team



Mobile: 305-965-2883

email: [login to unmask email]









Find me on: Twitter Linkedln World of Db2











From: "Bell, Raymond (Hosting Services, Technology)"

<[login to unmask email]>

To: "'[login to unmask email]'" <[login to unmask email]>

Date: 11/20/2018 08:35 AM

Subject: [DB2-L] - RE: Native RESTful service - BIND?







Their deployment can be automated via Endevor too, which is what we’re

working on doing. I meant automatic deployment via Postman in particular

(which is what we have at our disposal) would be difficult as it’s an

interactive process but until we have deployed the Db2 maintenance we need

that’s all we have right now.



From: Patrick Bossman [mailto:[login to unmask email]

Sent: 20 November 2018 12:20

To: [login to unmask email]

Subject: [DB2-L] - RE: Native RESTful service - BIND?









*********************************************

" This message originates from outside our organisation. Consider carefully

whether you should click on any links, open any attachments or reply. If in

doubt, forward to ~ Phishing"

*********************************************







Rest calls can be automated. We automated the deployment with UCD.



In Reply to Raymond Bell:

Hi Wolfgang,



First off, if you’re not bang up-to-date with Db2 maintenance I

suggest you be so. There’s an info APAR (II14827) that highlights a

few gems, but if you want any of the more useful bind parms to work

with BIND SERVICE (other than OWNER and QUALIFIER) you’ll need some.

Plus some PTFs to even get it to work at all.



So. I’m looking at using Endevor to manage the single SQL statement

REST service and have it perform the required BIND SERVICE to

register it. Any QA performed would be after the fact, as per any

other package that gets bound. Not sure about intercepting the bind

per se but you could certainly establish change management processes

to QA the package and get it signed off/modified before going above

Unit Test.



Have fun. And brace for a bumpy ride. An update I received in a V11

PMR I raised on REST bind options said, ‘…it's a relative new service

and is constantly improved…’ to which you could replace ‘improved’

with ‘being fixed’. Still it’s worth persevering with BIND SERVICE as

the alternative (off-host creation of services via something like

Postman) is quite fiddly, can’t really be automated and you have no

control over the bind options used – although of course you could

always rebind the package afterwards to get the parms you want.



Cheers,





Raymond





From: Wolfgang Beikircher [mailto:[login to unmask email]

Sent: 19 November 2018 14:45

To: [login to unmask email]

Subject: [DB2-L] - Native RESTful service - BIND?





*********************************************

" This message originates from outside our organisation. Consider

carefully whether you should click on any links, open any attachments

or reply. If in doubt, forward to ~ Phishing"

*********************************************





Hi there!



I attended the last IDUG on Malta and heard of the 'native RESTful

services' that were ported to V11. Actually we are searching for an

easy way to define standardized SQL queries from our 'distributed

programming people'. Today we have, at least for inhouse written

software, no dynamic SQL on Db2. If data is requested from Db2 there

has to be written a Stored procedure or a CICS/batch program.



Since we have just static SQL we could establish a quite good QA that

checks the statements already in our test environments. So far so

good.



Now to the question. Is there a way to intefere the creation of a

service (created through the native RESTful interface) to do some

checks for QA? I have an exit in mind, that allows us to perform some

explain.







Thanks



















-----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



-----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



Site Links: View post online View mailing list online Start new thread

via email Unsubscribe from this mailing list Manage your subscription





This email has been sent to: [login to unmask email]





ESAi has well-regarded tools for Fast Cloning, Buffer Pool Tuning, Log

Analysis, TDM & more.

BCV4, BCV5, BPA4DB2, ULT4DB2... modern power tools to get the job done

faster & easier than ever.

http://www.ESAIGroup.com/idug







Use of this email content is governed by the terms of service at:

http://www.idug.org/p/cm/ld/fid=2

















Attachments

  • 15496143.gif (<1k)
  • 15669681.gif (1.4k)
  • 15540432.gif (<1k)
  • graycol.gif (<1k)

Wolfgang Beikircher

RE: AW: Native RESTful service - BIND?
(in response to Walter Janißen)

Thanks guys for your comments.

 

Yes, we know that this functionality is pretty new to DB2. Also considering that we are still on V11 and IBM ported if from V12.

But sincerely, you lost me somewhere in the middle. Of course we can, lets say once every day at 11pm, extract all packages that were created and analyse them with BIND EXPLAIN(YES). But in my opinion this is the second best solution because I have to throw this particular 'user defined' service back to the developer. And the whole discussion starts.

More convenient for me would be the possibility to interfere the POST request to generate the service. As far as I know should the POST request generate me the package. If I have the package, I could explain the content. If it does not correspond to our standards, the BIND should be refused.

What about that?

 

 

 

Raymond Bell

AW: Native RESTful service - BIND?
(in response to Wolfgang Beikircher)
Not sure what bind control you get over the POST instruction, at least within Postman – which is the only REST client I’m semi-familiar with. Worst case scenario you could always allow the bind, do whatever due package diligence you need to and, if the package doesn’t meet your standards, free it and maybe –STO RESTSVC the service.

Or… if the REST service issues a CALL statement, rather than an individual DML SQL statement, you have nothing to worry about; all your QA work will be on the SP the REST service is CALLing. Obviously doesn’t help with single DML REST services.

Cheers,


Raymond

From: Wolfgang Beikircher [mailto:[login to unmask email]
Sent: 21 November 2018 11:11
To: [login to unmask email]
Subject: [DB2-L] - RE: AW: Native RESTful service - BIND?


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************


Thanks guys for your comments.



Yes, we know that this functionality is pretty new to DB2. Also considering that we are still on V11 and IBM ported if from V12.

But sincerely, you lost me somewhere in the middle. Of course we can, lets say once every day at 11pm, extract all packages that were created and analyse them with BIND EXPLAIN(YES). But in my opinion this is the second best solution because I have to throw this particular 'user defined' service back to the developer. And the whole discussion starts.

More convenient for me would be the possibility to interfere the POST request to generate the service. As far as I know should the POST request generate me the package. If I have the package, I could explain the content. If it does not correspond to our standards, the BIND should be refused.

What about that?







-----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