Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This documentation applies to when you want your query output to go to the CUNY Tumbleweeds server. This location allows for direct or scheduled download of output/report files.

Note

NOTE - This documentation picks up at the point you are setting the query run schedule, Process Scheduler Request. For details on getting to this point see General Query Scheduling Documentation

If the File option is selected in the Process Scheduler Request window, the Format and Distribution drop-down lists appear.  The file destination can be financial reporting or campus solution reporting. 

 

(warning) Please see hc003 or FS001 in navigation bar then the output destination will be -

HC003 (HCM/CS reporting)

sftpcsout/PSQUERY_OUT/Baruch

FS001 (financial reporting)

sftpfsout/PSQUERY_OUT/Baruch

 

 

Notes from Abu and Dixon - we'll translate these into the documentation

Panel

From: Abu Kamruzzaman
Sent: Wednesday, September 17, 2014 3:57 PM
To: Tabassum Lodhi
Cc: Patrick Ackerman; Dixon Berry
Subject: Scheduling Query with tumbleweeds

 

Hello Everyone,

I found that both query name and control id require the BAR tag. Otherwise, the query are not picked up in tumbleweed.

If control id don’t have BAR tag, you will see the Run Status “No Success”. If query name don’t have BAR tag, you will see the Run Status “Success” but the result don’t seem to appear in tumbleweed. Instance: 4947287 didn’t transfer to the tumbleweed.

Check attached images for reference.

I deleted most of the output except CU_BAR_SR_00001-4947289.csv which is a output of instance:4947289


On Sep 17, 2014, at 5:36 PM, "Dixon Berry" <Dixon.Berry@baruch.cuny.edu> wrote:

Well, my job CU_BAR_PR_00035 does come through onto Tumbleweed. My control ID is BAR~ but my query name is still CU_BAR~.

 

Note that if you have two identical Control ID in the system, neither are reliable in my experience. It’s difficult to know if you two identical IDs, the only way I know to find out is to do “Instance 1” to “Instance 9999999” in the Process Monitor and look for duplicates.

 

Also, clicking on the green swirl arrow will show you the run history for the job.


From: Abu Kamruzzaman
Sent: Wednesday, September 17, 2014 5:52 PM
To: Dixon Berry
Cc: Tabassum Lodhi; Patrick Ackerman
Subject: Re: Scheduling Query with tumbleweeds

As long as BAR tag appears anywhere in the query name it will work. My query name that worked also has CU as prefix.


From: Dixon Berry
Sent: Thursday, September 18, 2014 9:16 AM
To: Abu Kamruzzaman
Cc: Tabassum Lodhi; Patrick Ackerman
Subject: RE: Scheduling Query with tumbleweeds

OK, nice to know. By the way, it seems logical that the sequence number of the most recent file downloads would be higher than previous downloads, but that is not always the case. Only the file write date is reliable.

Issues with Scheduling

ISSUE occurs scheduling private query CU_BAR_SR_00035 - no queue is created

Note
titleIssue with Recurrence Resolved

The issue with the recurrence appears to be resolved. The recurrence we were testing was "M-F @7:00 AM", which would fail. We used an alternative recurrence named

"M-F at 7am" and the query ran and posted, and queued for the following day.

I notified Judith that we resolved and asked that she check the two recurrences for any differences.

CUNY CRM Case ID 388122

Troubleshooting CU_BAR_SR_00035

 

Warning
  • The data load to tumbleweed and receive file via Dixson's application.  Please check if the password is expired.
  • Check scheduling in CF reporting instances if the previous scheduling still on
  • STOP the previous scheduling immediately while setting up for current teamster.
QueryCU_BAR_SR_00035
Title/Description of the queryADID Updates Active Term Range
Pre-Condition
  • Send file to Tumbleweed folder location at: sftpcsout/PSQUERY_OUT/Baruch
    or Type Web 
  • Queue the same file for recurrence for everyday M-F@7AM
Test Steps (Scenario 1)
  1. Select to 'Schedule a query"
  2. Add new Run Control Id and click OK
  3. place all the desire prompt value.  In this case: Institution: BAR01, STRM_Form: 1169, STRM_To: 1169
  4. Click Run
  5. Set Recurrence M-F@7AM
  6. Choose File type: FILE; Format: TXT ; Distribution: sftpcsout/PSQUERY_OUT/Baruch
  7. Click OK
  8. Go to Process Monitor to check the status of the file.
Test Steps (Scenario 2)
  1. Add new Run Control Id and click OK
  2. place all the desire prompt value.  In this case: Institution: BAR01, STRM_Form: 1169, STRM_To: 1169
  3. Click Run
  4. Set Recurrence M-F@7AM
  5. Choose File type: WEB; Format: TXT ; Distribution: distribution
  6. Click OK
  7. Go to Process Monitor to check the status of the file.
Expected Results
  • The process list window will provide the information regarding file download.
  • Run Date/Time provides date and time to request for file.
  • Run Status should appear as 'Success for Today' and 'Queued for Next Day'
  • Detail will provide detail log information about file

Unexpected Results/Recommendation

 

 

 

 

 

 

 

 

 

According to scenario 1 & 2, the process FAILED to progress as 'Success' for Today and queue for 'Next day' as recurrence. 
NOTE: This query (CU_BAR_SR_00035) was replaced from original cu_bar_sr_00035 and recopied to other users.  The defects are still unknown and should recommend to generate CRM to Baruch Help desk for further assistance. 

CRM created - Case #388122 - Description provided:

Panel

I'm attempting to schedule private query CU_BAR_SR_00035 on recurrence schedule "M-F @7:00 AM". The schedule will initially trigger and run query immediately, but on completion (SUCCESS) will not show a queued schedule for the following day. This applies whether file type is web or file (output to folder for Tumbleweeds). The following day we will see a run of the query, but this will only occur for one day with no queued schedule for following day displayed.

This issue does not occur with other private queries.

Note that the only thing that may be unique about this query (CU_BAR_SR_00035) was that it was replaced from an original query with same name. The original query had been copied to me by user 23116688.

We had made a copy of CU_BAR_SR_00035, naming it CU_BAR_SR_00035_1. We then deleted CU_BAR_SR_00035 and renamed CU_BAR_SR_00035_1 to CU_BAR_SR_00035. When scheduling CU_BAR_SR_00035_1 the queue was created without any issue.

This same issue is experienced by other users we've tested with at Baruch.

ResolutionThe time need to set as M-F AT 8AM

 

The images have shown recurrence below: