Page 2 of 3

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Thu Jun 25, 2015 10:21 pm
by Pedro
Prino's earlier comment applies
[quote]And doubtlessly you put it into the correct profile variable in the correct profile?[/quote]
Many products use an application ID to have separate set of variables from each other, in order to avoid collisions in use of variable names.

Start file-aid using ISPF option 7, then use DTEST 3 command to examine profile variables. Look for ZAPPLID. Your exec has to also be invoked in that same applid or your variable will be saved in the wrong place.

note to moderator: whats up with quote tags not working?

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Mon Jun 29, 2015 6:14 pm
by mymainframe
Hi Pedro,

I checked in my shop and found ZAPPLID is ISR. What ZAPPLID should change to so, that I am able to VPUT in my ISPF profile.

Thanks.

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Mon Jun 29, 2015 11:27 pm
by Pedro
Repeating:
Your exec has to also be invoked in that same applid or your variable will be saved in the wrong place.

If Fileaid operates in the ISR applid, then make sure your exec also operates in the ISR applid.

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Tue Jun 30, 2015 11:19 pm
by prino
mymainframe wrote:I checked in my shop and found ZAPPLID is ISR. What ZAPPLID should change to so, that I am able to VPUT in my ISPF profile.

I would be extremely surprised (or, being the cynic I've become, I should probably be extremely unsurprised) if FileAid was set up to use the ISR ZAPPLID at your bodyshop.

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Mon Jul 27, 2015 8:49 pm
by mymainframe
Hi Prino,

ZAPPLID is IXP not ISR.

I am using ISR applid to autopopulate values on file aid screen. Before calling file aid (using CMD(xixmain) newappl(IXP) passlib) I am using VPUT to update file aid pannel variables also moving values to IXPPROF. Here I am getting below error when I execute my REXX.
****************************************
* ISPV006
* Data truncation occurred
* Data for char format variable "IXPPROF" was too long
*
*


Can you please suggest how can I correct this error.

Thanks

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Mon Jul 27, 2015 9:05 pm
by Pedro
I think you need to contact the Fileaid vendor.

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Mon Jul 27, 2015 9:07 pm
by mymainframe
One more, here before giving VPUT for IXPPROF, length was 1127. I am giving VPUT with a length of 262 and I can see that it got updated in IXPPROF variable (I confirmed by checking ISRPROF table using 3.16 utility). not sure why it is getting error out.

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Tue Jul 28, 2015 5:35 am
by Pedro
Show us your code.

I would expect the failure later, when Fileaid goes to use the value that you set. I do not expect an error at the time when you save the value.

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Tue Jul 28, 2015 11:45 am
by mymainframe
Yes Pedro, it is getting error when File-AID is using the variable. Below is the code.
IXPPROF = "Variable with a length of 1127 bytes"
"ISPEXEC VPUT (IXPPROF) PROFILE"
"ISPEXEC CMD(XIXMAIN) NEWAPPL(ISR) PASSLIB"


Here I tested the same using "Dialog Test --> 1.Functions --> Invoke command" option, even there I am getting same error. when I select " _ override termination and attempt to continue" then its going to File-AID and working fine.

Thanks.

Re: How dataset is auto populates in 3.4 Screen

PostPosted: Tue Jul 28, 2015 6:54 pm
by Pedro
Here I am getting below error when I execute my REXX.

You should strive to explain the situation more accurately in the future.

Rexx is flexible about the length the variable data. Compiled languages have to use VDEFINE prior to the VGET... the VDEFINE specifies the length of the data. Unless you can change the length and recompile the program, I think you have to adjust your data to use the acceptable length?

Who ever heard of a data set name that is so long anyway?