Journaling commands and SQL created objects

We have one system where the entire schema was created using SQL commands. Journaling was setup automatically. All was good. We then had a need to replicate the entire schema to a new name for a training so saved the production library and restored to the training library. That all appeared to work. All objects that were in the production schema were created in the training version. Including the journal object. What we didn't notice was that the training files were all attached to the journal in production. It worked but was not as it should be so we were doing a process of ending journaling on all the training library tables and access paths and reattaching them to the journal in the training library. Was on a command line using ENDJRNPF and ENDJRNAP then STRJRNPF and STRJRNAP. That all went OK until we hit an SQL view. The View object was showing as an LF type but neither ENDJRNPF or ENDJRNAP would work. Each said the object was not of the correct type. To get by the errors we had to delete the view in the training library and recreate it in the training library. I did not think about it until we were done but should we have done this process using Navigator or some way using STRSQL to adjust object journaling?

Thanks

Mike Cunningham