HLLX loging of users invoked HLLX functions | Rocket Forum

Status: Declined

Declined

Add to ZMF logging new log type records for users invoked HLLX calls for processes like create, stage, promote... right now we only seem to log ADMIN HLLX changes and attach/detach.

We have had HLLX abends and it is hard to tell functions that were running.

Also would be nice if a SERPRINT was added to HLLX to display same log records.

Add to ZMF logging new log type records for users invoked HLLX calls for processes like create, stage, promote... right now we only seem to log ADMIN HLLX changes and attach/detach.

We have had HLLX abends and it is hard to tell functions that were running.

Also would be nice if a SERPRINT was added to HLLX to display same log records.

I think i would model the ZMF log record after the log records for user stage/checkout...

user name, package, date and time and in text area the HLLX function invoked.

Page 1 / 1

Status: Declined

Declined

Add to ZMF logging new log type records for users invoked HLLX calls for processes like create, stage, promote... right now we only seem to log ADMIN HLLX changes and attach/detach.

We have had HLLX abends and it is hard to tell functions that were running.

Also would be nice if a SERPRINT was added to HLLX to display same log records.

Add to ZMF logging new log type records for users invoked HLLX calls for processes like create, stage, promote... right now we only seem to log ADMIN HLLX changes and attach/detach.

We have had HLLX abends and it is hard to tell functions that were running.

Also would be nice if a SERPRINT was added to HLLX to display same log records.

I think i would model the ZMF log record after the log records for user stage/checkout...

user name, package, date and time and in text area the HLLX function invoked.

John You can display all that information in the log of the HLLX task now when using REXX. The log is by invocation .. It creates a sys000? File for each invocation, that is how I debug all the HLLX programs. I haven't done much with the LE versions.

Status: Declined

Declined

Add to ZMF logging new log type records for users invoked HLLX calls for processes like create, stage, promote... right now we only seem to log ADMIN HLLX changes and attach/detach.

We have had HLLX abends and it is hard to tell functions that were running.

Also would be nice if a SERPRINT was added to HLLX to display same log records.

Add to ZMF logging new log type records for users invoked HLLX calls for processes like create, stage, promote... right now we only seem to log ADMIN HLLX changes and attach/detach.

We have had HLLX abends and it is hard to tell functions that were running.

Also would be nice if a SERPRINT was added to HLLX to display same log records.

I think i would model the ZMF log record after the log records for user stage/checkout...

user name, package, date and time and in text area the HLLX function invoked.

Upon review there are no plans to include the functionality requested here within any future version of the product. Many of the existing and planned HLLX points can be very frequently executed within the product. Logging of all calls to HLLX routines has been deemed excessive and could potentially flood any ZMF log or output file. The overall stability of the HLLX functionality has also been much improved in the ZMF 8.1.1.01 release. Also, as Tom states, customers do have the ability to add the diagnostics that they require within their own HLLX routines. If a customer does feel that some kind of logging is required then this can be achieved within the current architecture. Closing Idea as ‘Declined’ at this time.