Joblog please. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "David Morris" <David.Morris@plumcr To: <email@example.com> eek.com> cc: Sent by: Fax to: security400-admin@mi Subject: [Security400] Debug anomaly drange.com 03/14/2002 03:02 PM Please respond to security400 Group, While testing authority on our system, I noticed that I could not debug an ILE program that I felt I should be able to debug. I had *all authority to both the library and program from my group profile via ownership. I set my group profile via a swap and then tried it using the set effective group Unix API with the same result. I ran: strdbg pgm(grpownlib/grpownpgm) That failed. I can run strdbg and then hit F14 and add the program to debug, which is equivalent to the first command. This only happens for programs. Service programs do not exhibit this behavior and work as expected. Does anyone know if this is how it is supposed to work or is there a bug? David Morris _______________________________________________ This is the Security Administration on the AS400 / iSeries (Security400) mailing list To post a message email: Security400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/security400 or email: Security400firstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/security400.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.