× 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.



On 09-Sep-2011 15:31 , gn pr wrote:

I have the error: Pointer not set for location referenced using
QykmExportKeyStore

I have the next source code:

int
{
// [...] errorCode
// *SYSTEM storage path
main ()
char* volatile path = "/QIBM/USERDATA/ICSS/CERT/SERVER/DEFAULT.KDB";
int* volatile pathLength = newint( strlen ((char* ) path ) );
char* volatile format = "OBJN0200";
char* volatile pwd = "ff1";
int* volatile pwdLength = newint( 3 );
int* volatile ccsid = newint(0);
char* volatile exportPath = "/usr/me/export.pcks";
int* volatile exportLength = newint( strlen ((char*) exportPath ));
char* volatile formatExport = "OBJN0200";
char* volatile version = "*PKCS12V3";
char* volatile pwdExport = "bas1";
int* volatile expLength = newint(strlen ((char*) pwdExport ));

QykmExportKeyStore ( path, pathLength, format, pwd, pwdLength
, ccsid , exportPath, exportLength, formatExport, version
, pwdExport , expLength, ccsid, errorCode ) ;

//[...] deletereturn0 ;
}

When I execute the code , I have: CPFB729
and with dspjoblog: Pointer not set for location referenced

What could be the cause ? I guess, Is one of the pointers which are
parameters of function... but which? because all are declared and
initialized.

but I could not figure out the solution.

Any help is appreciated :)


The msgCPFB729 is not an expected response from that API. The actual spooled joblog may do much better to clarify the origin of the messages for anyone who might respond. Attempts to describe errors in the joblogs "in words" versus using the spooled job log are almost always woefully inadequate. A couple other thoughts...

The format specified is OBJN0200, yet the format OBJN0100 seems may have been intended.? That, because there is no apparent attempt to "include the QLG path name structure length in addition to the length of the path name itself." as the documentation suggests is required?

The CHAR(10) "version" appears to be set to only nine bytes of data.?

What about the error code parameter?

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.