|
Thanks for the tip, Michael. I tried that and the CRTPAGSEG fails with the same error so I guess I have a problem with my use of the API. I have trawled through the code but cannot find where the problem is. Does any kind soul have a working RPG program they would be willing to share? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of michael@xxxxxxxxxxxxxxxxxx Sent: 16 January 2006 17:41 To: Midrange Systems Technical Discussion Subject: RE: Printing bitmaps Try FTPing the stream file to the PF and then the CRTPAGSEG - see if you have the same problem. I'm wondering if it's in the CPYFRMSTMF. > -------- Original Message -------- > Subject: Printing bitmaps > From: "Savage Gordon" <gordon.savage@xxxxxxxxx> > Date: Mon, January 16, 2006 12:32 pm > To: <midrange-l@xxxxxxxxxxxx> > > Good afternoon all, > > > > I have seen quite a number of discussions around this subject, but have > what seems to be a 'new' problem! > > > > We have a mobile data system which uses PDAs and GPRS; part of that > process is collecting signatures which are placed in the IFS as bitmaps. > > > > I have an RPGLE program bound to the QIMGCVTI API which takes this file > in (declared as a stream file) and outputs it in AFPDS format to another > IFS file e.g.: > > CALL PGM(CVTBMP) PARM('/cognito/images/67.bmp' '/cognito/images/afp67') > > I think this is working OK (!) as the new stream file is created and has > data. > > > > I have a PF created with: > > CRTPF FILE(@MD123/SIGAFP) > > RCDLEN(32766) > > TEXT('Signature in AFP format') > > LVLCHK(*NO) > > > > And when I try to copy the stream file into this PF (the QIMGCVTI API > doesn't enable direct output to a PF) using: > > CPYFRMSTMF FROMSTMF('/cognito/images/afp67') > > TOMBR('/qsys.lib/@md123.lib/sigafp.file/sigafp.mbr') > > MBROPT(*REPLACE) > > CVTDTA(*NONE) > > STMFCODPAG(37) > > DBFCCSID(37) > > ENDLINFMT(*FIXED) > > TABEXPN(*NO) > > It completes quite happily; however these parameters are the only ones > that do not result in a 'CPIA082 - End of file found before physical end > of file' which is a worry! > > > > Carrying on regardless, when I now try to create the page segment with: > > CRTPAGSEG PAGSEG(@MD123/SIGNATUR) > > FILE(@MD123/SIGAFP) > > MBR(SIGAFP) > > It is not created and a diagnostic message (sev 30) is issued 'CPD88C0 - > SIGAFP in @MD123 not valid for creating a *PAGSEG' with a reason code 2. > > > > Would anyone be able to help, please? > > > > > > Regards, > > _________________________________________________ > > Gordon Savage > > IS/IT Technical Analyst > > Volvo Construction Equipment Limited > > Duxford > > Cambridge > > CB2 4QX > > > > *Telephone: +44 (0) 1223 251767 > > *Fax: +44 (0) 1223 832357 > > *E-Mail: gordon.savage@xxxxxxxxx > > > > http://www.volvoce.co.uk/ > > Registered in England with Registrar of Companies, No: 1673954 > > VAT No: GB 599 3041 08 > > > > This e-mail transmission inclusive of any attachments is confidential > and intended solely for the person or organisation to whom it is > addressed. > > It may also be privileged or otherwise protected from disclosure.If you > are not the intended recipient, please do not copy, distribute or > disseminate the information - but notify the sender and delete this > e-mail and any attachments from your system. > > Any views or opinions expressed in this message are those of the author > and do not necessarily represent those of Volvo Construction Equipment > Ltd. Although the Volvo e-mail infrastructure does implement anti-virus > controls, Volvo Construction Equipment Ltd. does not accept liability or > responsibility for any damage or loss whatsoever caused from any > computer bug or virus being passed on, or arising from alteration of > this e-mail or any attachment, and does not represent or warrant that it > or any attached files are free from computer viruses or other defects. > E-mails and any attached files are provided, and may be used, only on > the basis that the recipient assumes all responsibility for any loss, > damage or consequence resulting directly or indirectly from them or > their use. > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.