Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

It's not hard to admit errors that are [only] cosmetically wrong. -- J. K. Galbraith


computers / comp.sys.tandem / Re: positioning in key sequenced file

SubjectAuthor
* positioning in key sequenced filenjdreams Golda
`* Re: positioning in key sequenced fileJShepherd
 +- Re: positioning in key sequenced fileKeith Dick
 `* Re: positioning in key sequenced filenjdreams Golda
  `* Re: positioning in key sequenced fileKeith Dick
   `* Re: positioning in key sequenced filenjdreams Golda
    `* Re: positioning in key sequenced fileKeith Dick
     `- Re: positioning in key sequenced filenjdreams Golda

1
positioning in key sequenced file

<7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=563&group=comp.sys.tandem#563

 copy link   Newsgroups: comp.sys.tandem
X-Received: by 2002:a05:620a:44c9:b0:6ed:81ba:667f with SMTP id y9-20020a05620a44c900b006ed81ba667fmr14729959qkp.92.1666373731262;
Fri, 21 Oct 2022 10:35:31 -0700 (PDT)
X-Received: by 2002:a0d:c285:0:b0:354:deb2:1aaa with SMTP id
e127-20020a0dc285000000b00354deb21aaamr16983083ywd.4.1666373731022; Fri, 21
Oct 2022 10:35:31 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.tandem
Date: Fri, 21 Oct 2022 10:35:30 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=66.159.204.103; posting-account=KVmdDwoAAABfBNMBDVFjVW3sW0y-FtEa
NNTP-Posting-Host: 66.159.204.103
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>
Subject: positioning in key sequenced file
From: goldanjd...@gmail.com (njdreams Golda)
Injection-Date: Fri, 21 Oct 2022 17:35:31 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1105
 by: njdreams Golda - Fri, 21 Oct 2022 17:35 UTC

Need help,

How we can do the key positioning in FILE_SETKEY_ guardian call when the file is read in reverse.

Re: positioning in key sequenced file

<tiumd1$m54v$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=564&group=comp.sys.tandem#564

 copy link   Newsgroups: comp.sys.tandem
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: inva...@nowhere.com (JShepherd)
Newsgroups: comp.sys.tandem
Subject: Re: positioning in key sequenced file
Date: Fri, 21 Oct 2022 17:54:42 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <tiumd1$m54v$1@dont-email.me>
References: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
Injection-Date: Fri, 21 Oct 2022 17:54:42 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="2bf0c94c2ae20b44e203343bf74828b6";
logging-data="726175"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX180Vnrkrg8xviCuBWR8A5wIz52chAsOvt4="
Cancel-Lock: sha1:mp91CZ9jrj/YM0tZJnZHmF0s6a0=
 by: JShepherd - Fri, 21 Oct 2022 17:54 UTC

In article <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>,
goldanjdreams@gmail.com says...
>
>Need help,
>
>How we can do the key positioning in FILE_SETKEY_ guardian call when the
file is
> read in reverse.

Guardian Procedure Calls Reference Manual

https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=a00022744en_us

#include "$system.zsysdefs.zsysc"
#include <cextdecs>

#define POSITION_APPROXIMATE 0
#define POSITION_GENERIC 1
#define POSITION_EXACT 2
#define PRIMARY_KEY 0

error = FILE_SETKEY_(fnum, (char *)&key, (short)sizeof(key)
,PRIMARY_KEY
,POSITION_APPROXIMATE
,ZSYS_VAL_SETKEYOPT_READREVERSE
/*, compare length */);

Re: positioning in key sequenced file

<72bb8611-a2c3-4a90-832b-0b4c5a83a70dn@googlegroups.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=565&group=comp.sys.tandem#565

 copy link   Newsgroups: comp.sys.tandem
X-Received: by 2002:a05:620a:2018:b0:6ee:a96:3c9e with SMTP id c24-20020a05620a201800b006ee0a963c9emr16169208qka.18.1666412589925;
Fri, 21 Oct 2022 21:23:09 -0700 (PDT)
X-Received: by 2002:a0d:d5d4:0:b0:369:7b1b:1959 with SMTP id
x203-20020a0dd5d4000000b003697b1b1959mr7583264ywd.370.1666412589732; Fri, 21
Oct 2022 21:23:09 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.tandem
Date: Fri, 21 Oct 2022 21:23:09 -0700 (PDT)
In-Reply-To: <tiumd1$m54v$1@dont-email.me>
Injection-Info: google-groups.googlegroups.com; posting-host=98.42.228.104; posting-account=Lua_ZwoAAADivbVXQF8uKE7dZSUNm9vj
NNTP-Posting-Host: 98.42.228.104
References: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com> <tiumd1$m54v$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <72bb8611-a2c3-4a90-832b-0b4c5a83a70dn@googlegroups.com>
Subject: Re: positioning in key sequenced file
From: rkd...@gmail.com (Keith Dick)
Injection-Date: Sat, 22 Oct 2022 04:23:09 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2599
 by: Keith Dick - Sat, 22 Oct 2022 04:23 UTC

On Friday, October 21, 2022 at 10:54:44 AM UTC-7, JShepherd wrote:
> In article <7b4c3653-45c2-455a...@googlegroups.com>,
> goldan...@gmail.com says...
> >
> >Need help,
> >
> >How we can do the key positioning in FILE_SETKEY_ guardian call when the
> file is
> > read in reverse.
> Guardian Procedure Calls Reference Manual
>
> https://support.hpe.com/hpesc/public/docDisplay?
> docLocale=en_US&docId=a00022744en_us
>
>
> #include "$system.zsysdefs.zsysc"
> #include <cextdecs>
>
> #define POSITION_APPROXIMATE 0
> #define POSITION_GENERIC 1
> #define POSITION_EXACT 2
> #define PRIMARY_KEY 0
>
>
> error = FILE_SETKEY_(fnum, (char *)&key, (short)sizeof(key)
> ,PRIMARY_KEY
> ,POSITION_APPROXIMATE
> ,ZSYS_VAL_SETKEYOPT_READREVERSE
> /*, compare length */);

Although the link to the Guardian Procedure Calls manual that JShepherd includes currently works, HPE sometimes publishes new versions of a manual that are given different URLs, and sometimes rearranges the document library in other ways.

A way to find a document for the NonStop system that is likely to work for a longer amount of time is to go to this page:

www.hpe.com/info/nonstop-docs

then click on the link for the type of NonStop system (J-series or L-series),
then fill in appropriate keywords for a search to locate the manual you need.

The keywords can be words in the title of the manual or words in the body of the manual.

Re: positioning in key sequenced file

<f1438da4-af80-48ee-9b34-a8b33201ef0an@googlegroups.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=567&group=comp.sys.tandem#567

 copy link   Newsgroups: comp.sys.tandem
X-Received: by 2002:a05:6214:1c4d:b0:4b1:7a21:e26f with SMTP id if13-20020a0562141c4d00b004b17a21e26fmr27475925qvb.81.1666619371406;
Mon, 24 Oct 2022 06:49:31 -0700 (PDT)
X-Received: by 2002:a25:394:0:b0:6be:6645:c10f with SMTP id
142-20020a250394000000b006be6645c10fmr28076338ybd.449.1666619371143; Mon, 24
Oct 2022 06:49:31 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.tandem
Date: Mon, 24 Oct 2022 06:49:30 -0700 (PDT)
In-Reply-To: <tiumd1$m54v$1@dont-email.me>
Injection-Info: google-groups.googlegroups.com; posting-host=134.238.15.211; posting-account=KVmdDwoAAABfBNMBDVFjVW3sW0y-FtEa
NNTP-Posting-Host: 134.238.15.211
References: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com> <tiumd1$m54v$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f1438da4-af80-48ee-9b34-a8b33201ef0an@googlegroups.com>
Subject: Re: positioning in key sequenced file
From: goldanjd...@gmail.com (njdreams Golda)
Injection-Date: Mon, 24 Oct 2022 13:49:31 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2048
 by: njdreams Golda - Mon, 24 Oct 2022 13:49 UTC

On Friday, October 21, 2022 at 11:24:44 PM UTC+5:30, JShepherd wrote:
> In article <7b4c3653-45c2-455a...@googlegroups.com>,
> goldan...@gmail.com says...
> >
> >Need help,
> >
> >How we can do the key positioning in FILE_SETKEY_ guardian call when the
> file is
> > read in reverse.
> Guardian Procedure Calls Reference Manual
>
> https://support.hpe.com/hpesc/public/docDisplay?
> docLocale=en_US&docId=a00022744en_us
>
>
> #include "$system.zsysdefs.zsysc"
> #include <cextdecs>
>
> #define POSITION_APPROXIMATE 0
> #define POSITION_GENERIC 1
> #define POSITION_EXACT 2
> #define PRIMARY_KEY 0
>
>
> error = FILE_SETKEY_(fnum, (char *)&key, (short)sizeof(key)
> ,PRIMARY_KEY
> ,POSITION_APPROXIMATE
> ,ZSYS_VAL_SETKEYOPT_READREVERSE
> /*, compare length */);

Can you help me with the value of "ZSYS_VAL_SETKEYOPT_READREVERSE" referred here?

Re: positioning in key sequenced file

<d6381a55-a764-43af-8993-1e6466cb3e42n@googlegroups.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=568&group=comp.sys.tandem#568

 copy link   Newsgroups: comp.sys.tandem
X-Received: by 2002:a05:622a:15c7:b0:39b:2791:cd44 with SMTP id d7-20020a05622a15c700b0039b2791cd44mr27246074qty.676.1666621029406;
Mon, 24 Oct 2022 07:17:09 -0700 (PDT)
X-Received: by 2002:a05:6902:1287:b0:6b9:c2c8:9d3b with SMTP id
i7-20020a056902128700b006b9c2c89d3bmr30308887ybu.553.1666621029141; Mon, 24
Oct 2022 07:17:09 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.tandem
Date: Mon, 24 Oct 2022 07:17:08 -0700 (PDT)
In-Reply-To: <f1438da4-af80-48ee-9b34-a8b33201ef0an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=98.42.228.104; posting-account=Lua_ZwoAAADivbVXQF8uKE7dZSUNm9vj
NNTP-Posting-Host: 98.42.228.104
References: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>
<tiumd1$m54v$1@dont-email.me> <f1438da4-af80-48ee-9b34-a8b33201ef0an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d6381a55-a764-43af-8993-1e6466cb3e42n@googlegroups.com>
Subject: Re: positioning in key sequenced file
From: rkd...@gmail.com (Keith Dick)
Injection-Date: Mon, 24 Oct 2022 14:17:09 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3164
 by: Keith Dick - Mon, 24 Oct 2022 14:17 UTC

On Monday, October 24, 2022 at 6:49:32 AM UTC-7, goldan...@gmail.com wrote:
> On Friday, October 21, 2022 at 11:24:44 PM UTC+5:30, JShepherd wrote:
> > In article <7b4c3653-45c2-455a...@googlegroups.com>,
> > goldan...@gmail.com says...
> > >
> > >Need help,
> > >
> > >How we can do the key positioning in FILE_SETKEY_ guardian call when the
> > file is
> > > read in reverse.
> > Guardian Procedure Calls Reference Manual
> >
> > https://support.hpe.com/hpesc/public/docDisplay?
> > docLocale=en_US&docId=a00022744en_us
> >
> >
> > #include "$system.zsysdefs.zsysc"
> > #include <cextdecs>
> >
> > #define POSITION_APPROXIMATE 0
> > #define POSITION_GENERIC 1
> > #define POSITION_EXACT 2
> > #define PRIMARY_KEY 0
> >
> >
> > error = FILE_SETKEY_(fnum, (char *)&key, (short)sizeof(key)
> > ,PRIMARY_KEY
> > ,POSITION_APPROXIMATE
> > ,ZSYS_VAL_SETKEYOPT_READREVERSE
> > /*, compare length */);
> Can you help me with the value of "ZSYS_VAL_SETKEYOPT_READREVERSE" referred here?

What kind of help do you want? I believe it is defined in $system.zsysdefs..zsysc, which JShepherd's example code shows to include via the statement:

#include "$system.zsysdefs.zsysc"

If, for some reason, you don't want to use the various declarations provided in zsysc, look in the manual we referenced to find which bit must be turned on in the sixths argument to request positioning for reverse reading.

In addition to looking at the Guardian Procedure Calls manual we referenced, you might need to look at the Enscribe Programming manual to understand better how to use the Enscribe procedure calls (more than the Guardian Procedure Calls manual tells you). You can find the Enscribe Programming manual via the method I mentioned in my previous post.

Re: positioning in key sequenced file

<06a0c19e-a8a9-47cb-8a41-e0be05b2031en@googlegroups.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=569&group=comp.sys.tandem#569

 copy link   Newsgroups: comp.sys.tandem
X-Received: by 2002:a05:620a:24d5:b0:6ee:d4bb:e5ba with SMTP id m21-20020a05620a24d500b006eed4bbe5bamr27022135qkn.457.1666708842544;
Tue, 25 Oct 2022 07:40:42 -0700 (PDT)
X-Received: by 2002:a05:6902:1146:b0:6ca:8a4c:d030 with SMTP id
p6-20020a056902114600b006ca8a4cd030mr18750965ybu.156.1666708842323; Tue, 25
Oct 2022 07:40:42 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.tandem
Date: Tue, 25 Oct 2022 07:40:42 -0700 (PDT)
In-Reply-To: <d6381a55-a764-43af-8993-1e6466cb3e42n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=134.238.15.217; posting-account=KVmdDwoAAABfBNMBDVFjVW3sW0y-FtEa
NNTP-Posting-Host: 134.238.15.217
References: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>
<tiumd1$m54v$1@dont-email.me> <f1438da4-af80-48ee-9b34-a8b33201ef0an@googlegroups.com>
<d6381a55-a764-43af-8993-1e6466cb3e42n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <06a0c19e-a8a9-47cb-8a41-e0be05b2031en@googlegroups.com>
Subject: Re: positioning in key sequenced file
From: goldanjd...@gmail.com (njdreams Golda)
Injection-Date: Tue, 25 Oct 2022 14:40:42 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3524
 by: njdreams Golda - Tue, 25 Oct 2022 14:40 UTC

On Monday, October 24, 2022 at 7:47:10 PM UTC+5:30, rkd...@gmail.com wrote:
> On Monday, October 24, 2022 at 6:49:32 AM UTC-7, goldan...@gmail.com wrote:
> > On Friday, October 21, 2022 at 11:24:44 PM UTC+5:30, JShepherd wrote:
> > > In article <7b4c3653-45c2-455a...@googlegroups.com>,
> > > goldan...@gmail.com says...
> > > >
> > > >Need help,
> > > >
> > > >How we can do the key positioning in FILE_SETKEY_ guardian call when the
> > > file is
> > > > read in reverse.
> > > Guardian Procedure Calls Reference Manual
> > >
> > > https://support.hpe.com/hpesc/public/docDisplay?
> > > docLocale=en_US&docId=a00022744en_us
> > >
> > >
> > > #include "$system.zsysdefs.zsysc"
> > > #include <cextdecs>
> > >
> > > #define POSITION_APPROXIMATE 0
> > > #define POSITION_GENERIC 1
> > > #define POSITION_EXACT 2
> > > #define PRIMARY_KEY 0
> > >
> > >
> > > error = FILE_SETKEY_(fnum, (char *)&key, (short)sizeof(key)
> > > ,PRIMARY_KEY
> > > ,POSITION_APPROXIMATE
> > > ,ZSYS_VAL_SETKEYOPT_READREVERSE
> > > /*, compare length */);
> > Can you help me with the value of "ZSYS_VAL_SETKEYOPT_READREVERSE" referred here?
> What kind of help do you want? I believe it is defined in $system.zsysdefs.zsysc, which JShepherd's example code shows to include via the statement:
>
> #include "$system.zsysdefs.zsysc"
>
> If, for some reason, you don't want to use the various declarations provided in zsysc, look in the manual we referenced to find which bit must be turned on in the sixths argument to request positioning for reverse reading.
>
> In addition to looking at the Guardian Procedure Calls manual we referenced, you might need to look at the Enscribe Programming manual to understand better how to use the Enscribe procedure calls (more than the Guardian Procedure Calls manual tells you). You can find the Enscribe Programming manual via the method I mentioned in my previous post.

Thanks for all your help .

Can we follow the same for read reverse lookup for alternate key lookup ?

Re: positioning in key sequenced file

<5c6a6bb0-0ea8-40b5-94fd-7f33c1732ae7n@googlegroups.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=570&group=comp.sys.tandem#570

 copy link   Newsgroups: comp.sys.tandem
X-Received: by 2002:a05:620a:271f:b0:6d4:56aa:4385 with SMTP id b31-20020a05620a271f00b006d456aa4385mr27485585qkp.175.1666712371709;
Tue, 25 Oct 2022 08:39:31 -0700 (PDT)
X-Received: by 2002:a05:6902:1287:b0:6b9:c2c8:9d3b with SMTP id
i7-20020a056902128700b006b9c2c89d3bmr36109737ybu.553.1666712371453; Tue, 25
Oct 2022 08:39:31 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.tandem
Date: Tue, 25 Oct 2022 08:39:31 -0700 (PDT)
In-Reply-To: <06a0c19e-a8a9-47cb-8a41-e0be05b2031en@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=98.42.228.104; posting-account=Lua_ZwoAAADivbVXQF8uKE7dZSUNm9vj
NNTP-Posting-Host: 98.42.228.104
References: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>
<tiumd1$m54v$1@dont-email.me> <f1438da4-af80-48ee-9b34-a8b33201ef0an@googlegroups.com>
<d6381a55-a764-43af-8993-1e6466cb3e42n@googlegroups.com> <06a0c19e-a8a9-47cb-8a41-e0be05b2031en@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5c6a6bb0-0ea8-40b5-94fd-7f33c1732ae7n@googlegroups.com>
Subject: Re: positioning in key sequenced file
From: rkd...@gmail.com (Keith Dick)
Injection-Date: Tue, 25 Oct 2022 15:39:31 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4346
 by: Keith Dick - Tue, 25 Oct 2022 15:39 UTC

On Tuesday, October 25, 2022 at 7:40:43 AM UTC-7, goldan...@gmail.com wrote:
> On Monday, October 24, 2022 at 7:47:10 PM UTC+5:30, rkd...@gmail.com wrote:
> > On Monday, October 24, 2022 at 6:49:32 AM UTC-7, goldan...@gmail.com wrote:
> > > On Friday, October 21, 2022 at 11:24:44 PM UTC+5:30, JShepherd wrote:
> > > > In article <7b4c3653-45c2-455a...@googlegroups.com>,
> > > > goldan...@gmail.com says...
> > > > >
> > > > >Need help,
> > > > >
> > > > >How we can do the key positioning in FILE_SETKEY_ guardian call when the
> > > > file is
> > > > > read in reverse.
> > > > Guardian Procedure Calls Reference Manual
> > > >
> > > > https://support.hpe.com/hpesc/public/docDisplay?
> > > > docLocale=en_US&docId=a00022744en_us
> > > >
> > > >
> > > > #include "$system.zsysdefs.zsysc"
> > > > #include <cextdecs>
> > > >
> > > > #define POSITION_APPROXIMATE 0
> > > > #define POSITION_GENERIC 1
> > > > #define POSITION_EXACT 2
> > > > #define PRIMARY_KEY 0
> > > >
> > > >
> > > > error = FILE_SETKEY_(fnum, (char *)&key, (short)sizeof(key)
> > > > ,PRIMARY_KEY
> > > > ,POSITION_APPROXIMATE
> > > > ,ZSYS_VAL_SETKEYOPT_READREVERSE
> > > > /*, compare length */);
> > > Can you help me with the value of "ZSYS_VAL_SETKEYOPT_READREVERSE" referred here?
> > What kind of help do you want? I believe it is defined in $system.zsysdefs.zsysc, which JShepherd's example code shows to include via the statement:
> >
> > #include "$system.zsysdefs.zsysc"
> >
> > If, for some reason, you don't want to use the various declarations provided in zsysc, look in the manual we referenced to find which bit must be turned on in the sixths argument to request positioning for reverse reading..
> >
> > In addition to looking at the Guardian Procedure Calls manual we referenced, you might need to look at the Enscribe Programming manual to understand better how to use the Enscribe procedure calls (more than the Guardian Procedure Calls manual tells you). You can find the Enscribe Programming manual via the method I mentioned in my previous post.
> Thanks for all your help .
>
> Can we follow the same for read reverse lookup for alternate key lookup ?

Yes, the same code works for read reverse by an alternate key as long as you pass the alternate key's specifier in the fourth argument of the SET_FILEKEY_ call (and put the alternate key's value and length in the second and third arguments). The alternate key's specifier is the 16-bit value used to identify the alternate key when you create the alternate key. It usually is given as two ASCII characters in FUP commands, but don't specify it that way in the fourth argument to FILE_SETKEY_. The alternate key specifier must be a 16-bit value, not the address of a string.

Re: positioning in key sequenced file

<0c77e60c-8ce5-4066-a32b-99b3ab7a31a9n@googlegroups.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=573&group=comp.sys.tandem#573

 copy link   Newsgroups: comp.sys.tandem
X-Received: by 2002:a05:622a:201:b0:3a4:f466:9998 with SMTP id b1-20020a05622a020100b003a4f4669998mr6003774qtx.258.1666886932420;
Thu, 27 Oct 2022 09:08:52 -0700 (PDT)
X-Received: by 2002:a25:c4c4:0:b0:6cb:e38d:9d7e with SMTP id
u187-20020a25c4c4000000b006cbe38d9d7emr2087087ybf.29.1666886932104; Thu, 27
Oct 2022 09:08:52 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.tandem
Date: Thu, 27 Oct 2022 09:08:51 -0700 (PDT)
In-Reply-To: <5c6a6bb0-0ea8-40b5-94fd-7f33c1732ae7n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=66.159.204.102; posting-account=KVmdDwoAAABfBNMBDVFjVW3sW0y-FtEa
NNTP-Posting-Host: 66.159.204.102
References: <7b4c3653-45c2-455a-910e-bc2713415a92n@googlegroups.com>
<tiumd1$m54v$1@dont-email.me> <f1438da4-af80-48ee-9b34-a8b33201ef0an@googlegroups.com>
<d6381a55-a764-43af-8993-1e6466cb3e42n@googlegroups.com> <06a0c19e-a8a9-47cb-8a41-e0be05b2031en@googlegroups.com>
<5c6a6bb0-0ea8-40b5-94fd-7f33c1732ae7n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0c77e60c-8ce5-4066-a32b-99b3ab7a31a9n@googlegroups.com>
Subject: Re: positioning in key sequenced file
From: goldanjd...@gmail.com (njdreams Golda)
Injection-Date: Thu, 27 Oct 2022 16:08:52 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4598
 by: njdreams Golda - Thu, 27 Oct 2022 16:08 UTC

On Tuesday, October 25, 2022 at 9:09:32 PM UTC+5:30, rkd...@gmail.com wrote:
> On Tuesday, October 25, 2022 at 7:40:43 AM UTC-7, goldan...@gmail.com wrote:
> > On Monday, October 24, 2022 at 7:47:10 PM UTC+5:30, rkd...@gmail.com wrote:
> > > On Monday, October 24, 2022 at 6:49:32 AM UTC-7, goldan...@gmail.com wrote:
> > > > On Friday, October 21, 2022 at 11:24:44 PM UTC+5:30, JShepherd wrote:
> > > > > In article <7b4c3653-45c2-455a...@googlegroups.com>,
> > > > > goldan...@gmail.com says...
> > > > > >
> > > > > >Need help,
> > > > > >
> > > > > >How we can do the key positioning in FILE_SETKEY_ guardian call when the
> > > > > file is
> > > > > > read in reverse.
> > > > > Guardian Procedure Calls Reference Manual
> > > > >
> > > > > https://support.hpe.com/hpesc/public/docDisplay?
> > > > > docLocale=en_US&docId=a00022744en_us
> > > > >
> > > > >
> > > > > #include "$system.zsysdefs.zsysc"
> > > > > #include <cextdecs>
> > > > >
> > > > > #define POSITION_APPROXIMATE 0
> > > > > #define POSITION_GENERIC 1
> > > > > #define POSITION_EXACT 2
> > > > > #define PRIMARY_KEY 0
> > > > >
> > > > >
> > > > > error = FILE_SETKEY_(fnum, (char *)&key, (short)sizeof(key)
> > > > > ,PRIMARY_KEY
> > > > > ,POSITION_APPROXIMATE
> > > > > ,ZSYS_VAL_SETKEYOPT_READREVERSE
> > > > > /*, compare length */);
> > > > Can you help me with the value of "ZSYS_VAL_SETKEYOPT_READREVERSE" referred here?
> > > What kind of help do you want? I believe it is defined in $system.zsysdefs.zsysc, which JShepherd's example code shows to include via the statement:
> > >
> > > #include "$system.zsysdefs.zsysc"
> > >
> > > If, for some reason, you don't want to use the various declarations provided in zsysc, look in the manual we referenced to find which bit must be turned on in the sixths argument to request positioning for reverse reading.
> > >
> > > In addition to looking at the Guardian Procedure Calls manual we referenced, you might need to look at the Enscribe Programming manual to understand better how to use the Enscribe procedure calls (more than the Guardian Procedure Calls manual tells you). You can find the Enscribe Programming manual via the method I mentioned in my previous post.
> > Thanks for all your help .
> >
> > Can we follow the same for read reverse lookup for alternate key lookup ?
> Yes, the same code works for read reverse by an alternate key as long as you pass the alternate key's specifier in the fourth argument of the SET_FILEKEY_ call (and put the alternate key's value and length in the second and third arguments). The alternate key's specifier is the 16-bit value used to identify the alternate key when you create the alternate key. It usually is given as two ASCII characters in FUP commands, but don't specify it that way in the fourth argument to FILE_SETKEY_. The alternate key specifier must be a 16-bit value, not the address of a string.

Thank you :)

1
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor