topic Re: SP schedule & 85 char limit on path in Developers

SP schedule & 85 char limit on path

Cynthia_sas — Mon, 24 Jul 2006 23:01:29 GMT

A couple of student Q's from class today:

1) Can a stored process be scheduled via a client scheduler?
(The students mean SPs with %stpbegin/%stpend -- NOT DIStudio jobs -- is WRS the only way?? Could other client schedulers be made to work????)

2) In registering a stored process, a couple students mentioned that the path specification is limited to less than 85 characters. They have a path that is 85 chars and get an error saying something like "Invalid path". If they move SP to higher directory, no problem. So it looks like path is being truncated. Do you know this to be true as a bug and if so, is it planned on being fixed? It seems likely that path names can legitimately be GT 85 characters.

Thanks, in advance, for any feedback,
cynthia

Re: SP schedule & 85 char limit on path

schering — Wed, 26 Jul 2006 19:03:09 GMT

I hope I understood question 2 correctly.

I registered the stp with source code location as L:\My Projects\StoredProcessPgms\Misc\_123456789\_123456789\_123456789\_123456789\_123456789 (92 characters)

The stored process ran successfully in Stored Process Web, AMO and EG.
Message was edited by: schering at Jul 26, 2006 3:03 PM

Re: SP schedule & 85 char limit on path

Cynthia_sas — Wed, 26 Jul 2006 19:54:17 GMT

Thanks for that! What I found out (offline) is that the actual path limit is 256 chars, so we think that there was something else going one for #2 for our folks with the question.

I have heard from a few folks off-line on #1 and the answer is really that the stored processes are not meant to replace whatever existing batch processes you have in place to update files and/or create tables. In Web Report Studio, you CAN schedule a report to update however, and WRS report CAN contain stored processes. But the bottom line is not to think you need to replace all of your existing batch processes with stored processes.

cynthia