Our reporting server is installed on an AS400 and i'm trying to map a path to a windows shared folder to get some pictures.
This is the code i used when trying this on the windows server and it works good:

APP MAP IMAGES 'W:\pics'
APP PREPENDPATH IMAGES

I need to do the same from the reporting server on the AS400 to this directory:

/qntc/storagesrv/Pictures/Pics

I can ping and connect to the server from the command line.

This message has been edited. Last edited by: Joe Beydoun,

Your subject says "accessing a windows shared folder", but "/qntc/storagesrv/Pictures/Pics" doesn't look like a Windows path...

Joe, can you do this from AS400, outside WebFOCUS ?

It is, i used the MKDIR command to create the path.

Waz,

i can see the path to these files from the AS400:

Work with Object Links

Directory . . . . : /QNTC/storagesrv/Pictures/Pics - Website

Type options, press Enter.
2=Edit 3=Copy 4=Remove 5=Display 7=Rename 8=Display attribu
11=Change current directory ...

Opt Object link Type Attribute Text
item images DDIR
Pics - New.lnk DSTMF
000063.jpg DSTMF
000069.jpg DSTMF
000103.jpg DSTMF
000109.jpg DSTMF
000121.jpg DSTMF
000310.jpg DSTMF
000401.jpg DSTMF

So if the directory is there, is it session related?
Does it exist for the WebFOCUS processes ?

I'm not an AS400 person, but does the path need to be there prior to the WebFOCUS process being called?

Can you call th MKDIR command from with is WebFOCUS ?

A bit of testing to determine the state of play.

it's not session related, as long as the proper user is accessing it, it's available on the system permanently.

Unfortunately i'm also not well versed with the AS400 file system.

Ok, this worked:

APP MAP IMAGES /qntc/
APP QUERY IMAGES

Result:

BEGIN-APP-QUERY: images
10/01/2011 15.40.55 1200 storagesrv
END-APP-QUERY

I just can't get the full path name or anything beyond this.

This might be a windows security issue at this point.

I'll repost after poking our network admin to help me with some tests tomorrow.

Appreciate the help everyone.

I wouldn't be surprised if Windows security got in the way.

This is all set now, thanks everyone for the help. There was a password mismatch between the iseries and the windows server, so we're all set now.