Jump to content


bschroder

Member Since 20 Jan 2004
Offline Last Active Feb 07 2012 09:17 PM
-----

Topics I've Started

pro-iv record locking question

06 February 2012 - 02:15 PM

I have a question about record locking in pro-iv (superlayer). Pro-IV version 4.6000 5.3.8 Superlayer version 7.00000 r101.05


I have a paging screen where a user can modify records in a table.

I have another update function that reads through this same table in delete mode to try and process these records and delete them.

Once I go into a record in the paging screen, if I try and run the update function, it will just hang until I exit out of the paging screen (without any type of message), then it will finish.

I want to be able to ignore the record that is being locked and just process the remaining records in the update function.

I put DSEL in the after read error logic and record lock logic in the update function, but it doesn't seem to get to that code since I also have messages to display and they do not get displayed.

Even if I get out of the record in the paging screen and scroll down to other records, it seems to keep locks on one or more records.

Any suggestions on how to handle this? Thanks.

transparent logins - parameters

20 January 2004 - 07:47 PM

I'm working now with Pro-IV kernel 4.6 r518.
On older versions, I was able to use the reserved word XFERIN to pass parameters when starting up a pro-iv session.

Example:
something.piv -P SYS MDC VAR1 VAR2 VAR3 VAR4

Then, in the pro-iv function:

XFERIN(VAR1, VAR2, VAR3, VAR4)

But, using 4.6 r518, when I do the same thing, all I get is:

VAR1 = Pro32
VAR2, VAR3, VAR4 = blank

Is there a different command to pick up those passed variables or has this changed somehow? Any help would be appreciated.

Thank you.