RPG Built in values such as *YEAR

Use this board to ask questions or have discussions with other Rich Displays users.
Post Reply
chris_rover
Profound User
Posts: 88
Joined: Tue Jun 01, 2010 11:31 am
First Name: christopher
Last Name: williams
Company Name: banks dih limited
Phone: 592-226-9584
Address 1: thirst park
Address 2: ruimveldt
City: gerogetown
State / Province: Outside Canada/USA
Zip / Postal Code: 0000
Country: Guyana
Contact:

RPG Built in values such as *YEAR

Post by chris_rover »

Hi guys,
I have a program that has a profoundui version as well as a green-screen version.
when I view the value of *year on the green-screen version, I get "2014", but when I view the value of *year in profoundui, I get "2013".

also, I have another program which does some printer file over-riding, sending the printer file to specified outqs. when this is done from a green-screen program, the over-ride works perfectly. However, when done from a profoundui version, the overrides are ignored.

please help!
dennisw
Profound User
Posts: 37
Joined: Thu Oct 15, 2009 4:34 pm
First Name: Dennis
Last Name: Willett
Company Name: Toledo CLinic
Contact:

Re: RPG Built in values such as *YEAR

Post by dennisw »

*year is based on the start date of the job. Your ProfoundUI server was probably last started in 2013. You may have end and restart the ProfoundUI server.



It is better to use %DATE() rather thatn *DATE because %DATE() is the current date regardless of job date.

To get the current year use CURYR = %SUBDT(%DATE():*YEARS)
User avatar
Alex
Profound Logic Staff Member
Posts: 233
Joined: Fri Jan 04, 2008 12:10 pm
First Name: Alex
Last Name: Roytman
Company Name: Profound Logic Software
Contact:

Re: RPG Built in values such as *YEAR

Post by Alex »

And in regards to printer file overriding...

When running programs within the HTTP subsystem, generated spooled files can assigned to a separate job by the system, called the QPRTJOB. See here for some details: http://pic.dhe.ibm.com/infocenter/iseri ... prtjob.htm.

I believe you can fix this by change the OVRTPRF command to have OVRSCOPE(*JOB) and SPLFOWN(*JOB) as parameters.
Post Reply

Who is online

Users browsing this forum: No registered users and 10 guests