SMERRS / SMC090 Wish List

Asking all tech resources to share their wish list for things to include in SMERRS and/or to display in the SMC090 error window.

Thanks! Tim

Find more posts tagged with

Comments

salbritton

The contents of "stack" would be helpful in SMERRS, especially when trying to debug errors that occur within an API.

Legacy Contributor

It would be nice to have an inquiry to this instead of using LOOK. And maybe a report. In the past, we (our partner) had a report that the user could run to see who was getting errors and then aborting out.

Maybe have a way to give the file name and key (if a missing record) or the variable if it's an error 47/42. Anything that can help research, especially if it's after the fact.

Legacy Contributor

I'd like to see an alt key by program name and line number. To help find those lines that generate the most errors.

XA10 Release 2021_9_9.mp4

Legacy Contributor

That should be ProgName + ProgLine + ErrNo

Legacy Contributor

The inquiry would really be nice, and be able to sort on specifics like program ID, error number, user ID or date range.

mgreer

On systems that support it I always add the PID of the process causing an error 0. Soft Locking should also support this.

gsieker

To add to Mike's request, the PID of the process causing the error 0 could then be used to look up and display User and Program that is causing the lock. We've found this to be very helpful in helping users resolve locking conditions.

Legacy Contributor

got it - will be throwing that into SMERRS

Legacy Contributor

Gary, are you referring to tcb(87)? that's only available on Unix, right?

Legacy Contributor

thanks Mike. do you know a way to get the PID in windows?

Legacy Contributor

Jim - does that need to be by descending date too?

Legacy Contributor

David - agreed - if it's in a SMGCTL record, it can be exported to Excel instead of writing a report. agree?

Legacy Contributor

Marc - i agree. will consider how much additional work that is.

gsieker

As far as I know, that's correct. We have code in place that only looks up and displays the additional info on *ix systems.

Legacy Contributor

Yes, descending date would be nice.

Legacy Contributor

Inquiry / or report would be nice.. it's nice to show customers how often their users abort out of error's. We have had a few customers over the years request that and it has come in very handy when you are trying to make a point

mcohen

I do a lot of work with SF, I don't know if SMERRS comes into play or not, but quite often the issue is data related. It would be nice if the error and the source of the data is reflected in the log ie item number / whse-item record/ ship-via / tax code / shipto-record / arcust record. It would also be helpful if an email went to an Admin notifying them of a problem when it is data driven. Mostly these errors occur outside the vision of the FACTS users and many times get unreported.

dEPM-670_Series_Part 4_FICA in Medicare.mp4

Legacy Contributor

Eliminate the D-Dump. We can get it once we are in the code and when the user chooses it it just garbles the screen and confuses them.

When the user clicks E=Escape, put a 20-30 second timer on it. The users click it out of desperation when they don't know what it is for. Often they are in a Lock which would have timed out and gone on if they weren't sitting in a Escape Code prompt.

Use a soft port for the H-Hardcopy option. Users try to be nice, print it, and FAX/E-mail it to Support. Often the issue is with the channel (10) that the Hardcopy option makes worse.

Leave a larger memo field in the record and to be passed for generic on-demand use. It may be useful on recurring errors to store generic data to help track the specific record/field/data that the error occurred on.

0712131256598360.doc

Copyright © 2025 Infor. All rights reserved.