|
At least what I have found in V5R2: USER parameter: Specifies, if the user name is returned, the name of the CL variable that receives the name of the user profile associated with the job when the job was started. The user name is the second part of the qualified job name. The variable must be a character variable with a minimum length of 10 characters. If the user name has fewer characters than the variable allows, the value is padded on the right with blanks. CURUSER parameter: Specifies, if the user name is returned, the 10-character CL variable that receives the name of the current user profile. If the current user name has fewer characters than the variable allows, the value is padded on the right with blanks. I think that the basic difference here is that USER gets the user profile associated with the job and CURUSER gets the user profile associated at that specific point on the thread. If you notice, on the online explanation of the command, in Table 1 (Attribute, scope and Thread safety) you will see they are different in terms of the scope. HTH, Peter Vidal Pall Aeropower Corp. SR Programmer Analyst WWW.Pall.com / 727-539-8448, x2414 "A good player makes himself look good; a great player makes the team look good." Author unknown
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.