Tom Evans 2

I receive the following error message when trying to use the over command. i am migrating from 7.7.05 and 7.7.05 has no problem with these commands. This is used in a PDF STYLESHEETS CAN NOT SEQUENCE ACROSS OR OVER COLUMNS TABLE FILE FOC_LCPPF21R_6 SUM COMPUTE COUNT1/I5 = 1; NOPRINT BY FOC_LCPPF21R_6.SEG01.DEFENDANT_LAST_NAME NOPRINT BY FOC_LCPPF21R_6.SEG01.DEFENDANT_FIRST_NAME NOPRINT BY FOC_LCPPF21R_6.SEG01.CASE_NUMBER NOPRINT BY FOC_LCPPF21R_6.SEG01.FILING_DATE_CCYYMMDD NOPRINT PRINT FOC_LCPPF21R_6.SEG01.DEFENDANT_LAST_NAME NOPRINT FOC_LCPPF21R_6.SEG01.CASE_NUMBER NOPRINT FOC_LCPPF21R_6.SEG01.CASE_NUM_SUB SKIP-LINE AS ARREST NUMBER: FOC_LCPPF21R_6.SEG01.CASE_DEF_SUBS NOPRINT FOC_LCPPF21R_6.SEG01.CHRG_DEF_SUBS NOPRINT FOC_LCPPF21R_6.SEG01.LOWER_COURT_NUMBER_10_20 AS CASE NUMBER: FOC_LCPPF21R_6.SEG01.DRUG_TYPE AS OVER FOC_LCPPF21R_6.SEG01.DEFENDANT_NAME AS NAME: FOC_LCPPF21R_6.SEG01.FILING_DATE_CCYYMMDD AS FILING DATE: FOC_LCPPF21R_6.SEG01.CLOSING_DATE_CCYYMMDD AS CLOSING DATE: OVER FOC_LCPPF21R_6.SEG01.STATUTE_ID AS FILED: FOC_LCPPF21R_6.SEG01.STATE_CODE AS FOC_LCPPF21R_6.SEG01.STATUTE_CLASSIFICATION AS FOC_LCPPF21R_6.SEG01.STATUTE_MEDIUM_DESCRIPTION#1 AS OVER FOC_LCPPF21R_6.SEG01.FINAL_STATUTE AS FINAL: FOC_LCPPF21R_6.SEG01.AMMENDED_STATE_CODE AS FOC_LCPPF21R_6.SEG01.AMMENDED_STATUTE_CLASSIFICATION AS FOC_LCPPF21R_6.SEG01.AMMENDED_STATUTE_MEDIUM_DESCRIPTION#1 AS OVER FOC_LCPPF21R_6.SEG01.PROS_ATTY AS PROSECUTOR: FOC_LCPPF21R_6.SEG01.DEF_ATTY AS DEFENSE: OVER FOC_LCPPF21R_6.SEG01.JUDGE_NAME AS JUDGE: FOC_LCPPF21R_6.SEG01.DISPOSITION_TYPE NOPRINT AS DISPOSITION,TYPE OVER FOC_LCPPF21R_6.SEG01.DISPOSITION_DESCRIPTION AS DISPOSITION: OVER FOC_LCPPF21R_6.SEG01.CLOSING_DATE NOPRINT AS CLOSING,DATE FOC_LCPPF21R_6.SEG01.RECORD_STAT_OPEN_CLOSED_HISTOR NOPRINT FOC_LCPPF21R_6.SEG01.SENTENCE_CONCAT AS SENTENCE: FOC_LCPPF21R_6.SEG01.CONSEC_CONCUR AS BY FOC_LCPPF21R_6.SEG01.DEFENDANT_LAST_NAME NOPRINT BY FOC_LCPPF21R_6.SEG01.DEFENDANT_FIRST_NAME NOPRINT BY FOC_LCPPF21R_6.SEG01.CASE_NUMBER NOPRINT BY FOC_LCPPF21R_6.SEG01.FILING_DATE_CCYYMMDD NOPRINT ON FOC_LCPPF21R_6.SEG01.CASE_NUMBER RECAP CASE_NUMBER/I6 = COUNT1; TOTAL_CASES/I6 = COUNT1; ON FOC_LCPPF21R_6.SEG01.CASE_NUMBER SUBFOOT WITHIN " " ON FOC_LCPPF21R_6.SEG01.CASE_NUMBER NOSPLIT HEADING " " City Prosecutor Full Case Description Crime Category &CATEGORY &CASEDROPDOWN6<+0> CASES "From <+0>&START_RPT6<+0> Through <+0>&END_RPT6<+0> " "&DATEtrMDYY <+0> " FOOTING LCPPF20R_FULL_CASE_BY_CRIME_TYPE ON TABLE SUBFOOT " " Total Cases: <CT.COUNT1 ON TABLE SET PAGE-NUM ON ON TABLE NOTOTAL ON TABLE PCHOLD FORMAT PDF ON TABLE SET HTMLCSS ON ON TABLE SET STYLE * UNITS=IN, PAGESIZE=Letter, LEFTMARGIN=0.638889, RIGHTMARGIN=0.430556, TOPMARGIN=0.750000, BOTTOMMARGIN=0.138889, SQUEEZE=ON, ORIENTATION=PORTRAIT, $ DEFMACRO=HEADING1, FONT=TIMES NEW ROMAN, SIZE=12, COLOR=BLUE, STYLE=BOLD+ITALIC, $ DEFMACRO=HEADING2, FONT=TIMES NEW ROMAN, SIZE=12, COLOR=BLUE, STYLE=BOLD+ITALIC, $ DEFMACRO=TITLES, FONT=TIMES NEW ROMAN, SIZE=8, COLOR=BLUE, STYLE=BOLD+ITALIC, $ DEFMACRO=BODY, FONT=IBIDEFAULT, SIZE=8, $ DEFMACRO=FOOTING, FONT=IBIDEFAULT, SIZE=6, $ TYPE=REPORT, GRID=OFF, TOPGAP=0.000000, MACRO=BODY, $ TYPE=SUBFOOT, BACKCOLOR=SILVER, STYLE=BOLD, MACRO=BODY, $ TYPE=SUBTOTAL, BACKCOLOR=SILVER, STYLE=BOLD, MACRO=BODY, $ TYPE=GRANDTOTAL, BACKCOLOR=SILVER, STYLE=BOLD, MACRO=BODY, $ ENDSTYLE END

We are upgrading to the cloud. I will check with out Network team. I believe they have looked at the firewall. We are not using a dedicated pipe to pass the data to and from the cloud. I believe we are using a VPN connection.

We are upgrading to 8.2.07 in the AWS cloud. Reporting that has a large amount of data to process has been timing out. Has anyone found a solution to issues with the AWS cloud performance.

I have a date in YYMD format on my table. When I try to compare it to a parameterized date in 8.2.07 it errors out. This compare worked fine in 7.705. We are upgrading to 8.2.07 and this code no longer works WHERE ( EVENT_DATE EQ &tbdtyymda10.(|FORMAT=YYMD).tbdtyymda10.QUOTEDSTRING ); WebFOCUS Error Executing body { font-family: Tahoma, Geneva, sans-serif; color: #464C57; margin: 0; text-align: center; } .errorContainer { display: block; flex-direction: column; justify-items: center; justify-content: flex-start; align-items: center; max-width: 600px; margin: auto; } .errorTitle { font-size: 20px; display: block; margin: 30px 20px 0 } .errorMain { font-size: 18px; display: block; margin: 30px 20px 0 } .errorMore { font-size: 14px; text-align: left } .errorMsg { font-size: 14px } .errorList { font-size: 14px } .errorDetail { font-size: 14px; display: block; margin: 0 20px 10px; flex-direction: column; text-align: left } pre { text-align: left; color: #666; font-size: 12px; font-weight: normal; margin: 5px 0 10px } pre b { font-weight: normal; } .showDetail { font-size: 14px; margin-top:10px } a:link, a:visited, a:active { color: #337ab7; text-decoration: none } a:hover { text-decoration: underline } h5 { text-align: left; margin: 10px 0 0; } (FOC1400) SQLCODE IS -22 (HEX: FFFFFFEA) : [s1000] [TOD][ODBC][GENESIS](pos: 433 'ENT_DATE" = ^DATE(2020-0) : - syntax error L (FOC1405) SQL PREPARE ERROR. (FOC1400) SQLCODE IS 1400 (HEX: 00000578) (FOC1500) : SQLCODE IS -22 (HEX: FFFFFFEA) L (FOC1406) SQL OPEN CURSOR ERROR. : PUBLIC_EVENTCASE

This ended up being an issue with the . acx file in the metadata. I recreated the synonym in 8.2.07 and the procedure worked. The error message it threw referencing the date took me down the wrong path. Partly my error though for not checking the metadata.

Hi John Thanks for your input. We havent had a great deal of errors with syntax. Ours have been with connectivity. We have resolved that and are moving fexes one by one. We are also going to the AWS cloud with this upgrade. Were getting a lot of 504 errors where there isnt a fast enough response between servers. We havent tried any HTML, ReportCaster or Portal at this point.

Hi Toby, I went through the Migration manual. I can see that in order to make the move to 8207 we are going to need some kind of professional services. We dont have a good grasp on the environment we are moving to so, we will have trouble configuring the data and reporting in a way that is efficient and well thought out.

As long as Im included in the conversation, I am fine with it being in an Administrative topic. I just wanted to get feedback from people who are in my situation or have been through the upgrade process. Even the responses I have received to this point has been very enlightening. I started the migration manual yesterday afternoon but havent gotten very far. I will continue to work my way through it. Again I really appreciate everyones feedback.

Thanks for all of the feedback. Can anyone tell me about the Change Management tool. Am I going to have to go to a later release like 8105 and then to 8207 or can I go directly to 8207 from 7705. Ive been working with IBI and we havent spoken about the CM tool yet. I use a lot of case sensitive variables and procedure names. Is the new release going to break those naming conventions.

We are on a mainframe IMS and DB2 and server for SQL. We run a Unix and Windows install. The Windows install is only for one application.

We are on 7.7.05 We are using Business Intelligence Dashboards (BID) We use HTML pages created in Dev Studio for those Dashboards We also use ReportCaster a lot. We have a small group of power users in InfoAssist We have only spoken at a high level about the security differences.

Thank you Chuck. Ill let you know if I have any questions.

Im looking for developers who are upgrading from 7.705 or similar to 8.2.07. Trying to find answers to questions about moving fexes and HTML to the new release.

Hello Robert I am in the same boat as Anthony and you. We are moving from 7.705 to 8.2.12. Dev Studio to App Studio. Anthony can you tell me anything about their migration tool. I would be really interested in any documentation you have found. We are also going to the AWS cloud.