List of Contributions

Sue BAYLISS

Contact Details

My Content

1 to 17 of 17 total
Posted By Sue BAYLISS Feb 4, 2021 12:05 PM
Found In Egroup: z/OS Connect Enterprise Edition
\ view thread
@Rahul Hi Rahul, Apologies for the delay in replying to your question. Which version of z/OS Connect EE are you using? This message (& similar messages) were corrected in ​z/OS Connect EE version 3.0.35 to no longer include the server URL. Regards, ------------------------------ Sue Bayliss ...
Posted By Sue BAYLISS Oct 7, 2020 7:05 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, Version is not currently returned for services. For details of which values are expected to be returned see Get details of a service . Regards, Sue ------------------------------ Sue Bayliss IBM z/OS Connect EE ------------------------------
Posted By Sue BAYLISS Oct 1, 2020 11:58 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, Please see my post number 4 above. The JSON is case sensitive. Please try using: --data '( "SQREQ": ( "ITEM_ID": 2033 ))' Regards, Sue ------------------------------ Sue Bayliss IBM z/OS Connect EE ------------------------------
Posted By Sue BAYLISS Oct 1, 2020 11:55 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, That documentation is correct, but as mentioned above, it is in the section of the Knowledge Center related to building a MQ service provider service using the command line build toolkit, which produces different request and response schemas. "For compatibility with earlier releases, MQ ...
Posted By Sue BAYLISS Sep 25, 2020 3:57 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, When using a TLS certificate and a safRegistry to authenticate to a z/OS Connect EE server the SMF values will be as you are seeing: SMF123S1_USER_NAME = the authenticated user name (SAF user ID) associated with the certificate SMF123S1_USER_NAME_MAPPED = will be blank This is ...
Posted By Sue BAYLISS Sep 23, 2020 3:27 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, --data '( "SQREQ": ( "ITEM_ID": 2033 ))' will work. But the case of the JSON field names is significant, in this example, uppercase. The request data must match what is expected by the service request schema. You can view the request schema for a service using the URI: /zosConnect/services/ ...
Posted By Sue BAYLISS Sep 22, 2020 5:38 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, This problem is caused by the request payload being sent to the service not matching the JSON schema that the service expects. If you are using the MQ service provider sample stockQuery.sar file shipped with the sample server template sampleMqStockManager, change the payload you send on ...
Posted By Sue BAYLISS Sep 22, 2020 3:37 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, Sorry, there was a typo on line 43 of the TwoWayBackend.java program in the product documentation, it should be: if (requestMessage == null) ( We will fix that. Thank you for your suggestion to ship the sample java application, we will take this into consideration. FYI: When using ...
Posted By Sue BAYLISS Sep 22, 2020 3:10 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin and Pitcho, We will investigate why you received that exception and improve the product behaviour. Please can you retry your curl POST request, but additionally including a request payload to be sent to the service: For example, if you are using the MQ service provider sample stockQuery.sar ...
Posted By Sue BAYLISS Sep 21, 2020 10:24 AM
Found In Egroup: API Enablement
\ view thread
This question is being investigated by the IBM z/OS Connect EE team. ------------------------------ Sue Bayliss IBM z/OS Connect EE ------------------------------
Posted By Sue BAYLISS Sep 21, 2020 10:23 AM
Found In Egroup: API Enablement
\ view thread
Hi Bart, One of the administrators of this IBM Z and LinuxONE Community explained that the first post anyone makes, is sent for verification before it appears (to ensure that the post is not from a robot), hence there can be a delay in posts appearing. Unfortunately, due to people being unavailable, ...
Posted By Sue BAYLISS Sep 17, 2020 4:20 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, I've forgotten where you can look up IBM Java SDK for z/OS release numbers. But fairly sure that is IBM Java 8 SR5 SDK for z/OS. SR6 which had the fix reported (output from java -version) as "Java(TM) SE Runtime Environment (build 8.0.6.0 - pmz6480sr6-20191107_01(SR6))". Regards, Sue ...
Posted By Sue BAYLISS Sep 16, 2020 6:34 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, What level of java are you using to run your z/OS Connect EE server? There was an issue in the JVM which could cause Java Segmentation errors during configuration updates, but that was fixed in IBM Java 8 SR6 SDK for z/OS. Regards, Sue ------------------------------ Sue Bayliss IBM z/OS ...
Posted By Sue BAYLISS Sep 16, 2020 6:23 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, The zosConnectApiRequester trace component is only applicable when you are using the z/OS Connect EE API requester function and have enabled the zosconnect:apiRequester-1.0 feature in the featureManager section of your server.xml configuration file. Regards, Sue ------------------------------ ...
Posted By Sue BAYLISS Sep 16, 2020 6:19 AM
Found In Egroup: API Enablement
\ view thread
Hi Colin, RE: The authority under which MQ requests run, information on how you can configure the MQ service provider to use a username and if required a password are documented in " Security requirements for the IBM MQ service provider ". Regards, Sue IBM z/OS Connect EE
Posted By Sue BAYLISS Sep 15, 2020 12:21 PM
Found In Egroup: API Enablement
\ view thread
Hi Colin, In general, the authorization groups (adminGroup, operationsGroup, invokeGroup & readerGroup) specified on the individual zosConnectAPI or service elements take precedence over the global groups (globalAdminGroup, globalOperationsGroup, globalInvokeGroup & globalReaderGroup) specified ...
Posted By Sue BAYLISS Sep 15, 2020 12:14 PM
Found In Egroup: API Enablement
\ view thread
FYI: This was a duplicate response (my original response had not appeared after several hours and I thought it had not worked so re-posted, this is the closest I can get to deleting the duplicate response).