Ok. This confuses me.  In script maker it shows popup which lists which steps are compatible.  It says:  server.

So is that 'server' when I am writing a PSOS or 'server' when I am writing a script to run as nightly server scheduled script?  I searched.  I really did.  For a full hour and 20 minutes!

So I read that PSOS is just like a client so the script compatibility for server must mean server scheduled scripts.  At least I think that is what it means.  And any step which can be used for Mac can be used for PSOS.  Please correct me if wrong.

Scheduled scripts and, Perform Script on Server are the same -  in the sense the filter for scripts that will work server side.

When you PSOS you are like a client logging in and all the operations that your startup script perform will trigger - so you may need to test your scripts if there are things you don't wish to happen on startup when starting up on server - if you have a HALT step for instance in your startup script then any script you set to PSOS will never execute, because your start up halts.

When you PSOS you will have to manage means to establish context (layout) and found set / sort order if needed perform the script  on a particular set of records. 

 

 

Edited June 18, 201510 yr by Ocean West

So I read that PSOS is just like a client so the script compatibility for server must mean server scheduled scripts. 

Nope.

Even a server-side schedule is "like a client".  In the sense that it spins up small virtual client session on the server.  But that client session does not have all the features or regular FMP.  It can only support the "server compatible" script steps.

Perfectly clear.  Thank you Ocean West and Wim Decorte both for the wonderful answers.  I think I will need to add Set Error Trap[on] before each step to try to find out if there is a problem since I can not see it run.  Or is there a way to watch it while it runs?  Debug does not seem to show it which is major dud.

Can I write each script step to a log of some sort and error trap each step and see what it actually does so I can SEE what I can not see?  I read I can look at server logs for scheduled scripts but all I see is 101 which is when loop exits but I have no way of knowing if it wrote properly to every record I said to change or if I failed in the record lock test or if it even sorted right.

I am begging my parents for loan of money to go to DevCon.  So far, they just laugh at me.  Some day they will not laugh and neither will my boss-o boss who spends more time looking at his reflection in the window than at his work.  I will laugh last.

If there were other errors they would show up in the event log.  Not a bad idea to do some of your own logging.

Note the behavior described here when FMS encounters an unspported script step: http://www.filemaker.com/help/13/fmp/en/html/create_script.13.8.html