× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: triggers & s36 update pgms
  • From: ken shields <kjs@xxxxxxxxxxx>
  • Date: Fri, 11 May 2001 06:47:38 -0400

The S/36 environment works slightly different than most of the 400 machines, for example, I'm not sure it recognizes a data base..db2 etc, as most of it's file structures were 'flat' or 'indexed'.
I doubt also, that you'll find anything that resembles a trigger in the 36 arena.
My guess is you may have to code a work around , which triggers a Cl access to a 36 program execution, passing a record as parm. The 36 program, simply, would read the record, update the file, and then LR.
Hope this helps, the folks at IBM ported the 36 environment, I suspect, because there were, as in my case, a lot of accounts, which still ran their systems on the S36 and did not upgrade through the years, (cost savings I guess)
I tend to look at it a dual personality,,,something akin to mental illness...
Ken

Jim Franz wrote:

Is there any known problems with a trigger pgm on a file updated by various pgms,including s36 screen & batch, rpg3 & rpg4 & rpgsql? Error is cpf502B, very vague.Only halting when s36 pgm was involved, and not halting on every update.Previous msg in joblog indicates reference to missing or deleted object,but doesn't say what it was looking for.At V4R4 cum 00350 and very old databasegroup ptf (from 99) - any help appreciatedjim

--
Best Regards
Ken Shields
Home phone: 905 404-2062
Bus  phone  905 725-1144 (326)
 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.